Adeptia MCP Server
Model Context ProtocolConnect Claude, ChatGPT, VS Code or any MCP client to Adeptia Automate.
Connect an MCP client
This endpoint accepts MCP protocol requests via HTTP POST. Configure your MCP client to use this URL.
A GET with a non-browser Accept header, such as text/event-stream, is answered 405 Method Not Allowed: the server offers no server-push stream here, and MCP clients should expect that.
Endpoint URL
/mcp
Authentication
// OAuth 2.1 Bearer Token Authorization: Bearer <token> // Your MCP client handles the OAuth flow automatically. // Discovery: GET /.well-known/oauth-authorization-server
Rate limits
// Requests per hour, fixed window. X-RateLimit-Limit on each response names the bucket. // OAuth Bearer token: 1000 per token. X-Adeptia-Api-Key: 1000 per key. // X-Adeptia-Username / -Password: 1000 per verified user; deprecated (no removal date), // use a key or OAuth; replacement: MCP-037. No usable credential: 20 per IP. Login form: 5 per minute per IP.
Example request body
{
"jsonrpc": "2.0",
"method": "tools/list",
"id": 1
}