/mcp.
Prerequisites
Before connecting an agent, make sure you have:- A project in the Devctrl console
- At least one MCP server registered with tools
- An identity with a credential
- An active policy release
Connection setup
- Claude Desktop
- Claude Code
- MCP Inspector
- Custom agent
Add Devctrl as an MCP server in your Claude Desktop configuration:Claude will discover tools from the gateway automatically via
tools/list.Adding task context
To use Task-Based Access Control, include a task token in your requests:- Create a task session via the Task Sessions API
- Add the
X-Task-Tokenheader to your MCP requests
X-Task-Token: YOUR_TASK_TOKEN as an additional header alongside your Authorization header.
In code, include the header in your transport configuration:
Troubleshooting
401 Unauthorized
401 Unauthorized
403 Forbidden — MCP not enabled
403 Forbidden — MCP not enabled
MCP is disabled for this project. Enable it in Project Settings.
403 Forbidden — Policy denied
403 Forbidden — Policy denied
The policy engine denied the tool call. Check:
- The active policy release in the console
- The identity’s labels match what the policy expects
- If using task tokens, ensure the task context is correct
- View the specific denial reason in Executions
429 Too Many Requests
429 Too Many Requests
Rate limit exceeded. The response includes which level was hit:
- Session: your agent is making too many calls. Space out requests.
- Project: all agents in this project have exceeded the project limit.
- Global: the gateway’s global limit was hit.
Tool not found
Tool not found
The tool doesn’t exist or isn’t visible to this identity. Check:
- The tool is registered under an MCP server in the project
- The identity’s
allowedToolslist includes this tool (or is unrestricted) - The upstream MCP server is healthy