MCP integration
Connect Devin to PrompTessor MCP
Add PrompTessor as a custom remote MCP server in Devin.
Verified against the implementation ·
Devin
Add PrompTessor as a custom remote HTTP server in Devin. OAuth is completed in the browser after the configuration is saved; do not use a PrompTessor REST API key as an authentication header.
Open Settings > Connections > MCP servers and select Add a custom MCP.
- 1
Open MCP servers
In Devin, go to Settings > Connections > MCP servers. Adding and authenticating a custom server requires the Manage MCP Servers permission.
- 2
Create a custom server
Select Add a custom MCP. Enter PrompTessor as the server name and add a short description such as “Prompt generation and management tools.”
- 3
Choose HTTP transport
Select HTTP (Streamable HTTP), paste the Server URL shown below, and choose OAuth as the authentication method.
- 4
Save before testing
Save the configuration. The Test listing tools action remains disabled until the custom server has been saved.
- 5
Authorize and test
Select Test listing tools, open the authorization URL, sign in to PrompTessor, and approve the requested scopes.
- 6
Verify in a session
Start a Devin session and ask it to check your PrompTessor usage. A get_usage result confirms the integration.
- Server name
PrompTessor- Server URL
https://mcp.promptessor.com/mcp- Transport
HTTP- Authentication
OAuth- Headers
None
Choose the access model deliberately
With Personal access, each member authorizes their own PrompTessor account. With Organization access, all members use the same authenticated connection; use a dedicated service account rather than a personal account for shared access.