Connect Claude to the hosted Agiler MCP server with a custom remote connector. Have an Agiler API key ready; projects:read is enough for the first verification task.

Add the connector

  1. Open Customize → Connectors in Claude.

  2. Choose Add → Add custom connector and name it Agiler.

  3. Enter https://mcp.agiler.io/v1 as the remote MCP server URL and continue.

  4. Review the authentication settings. Select No sign in for the OAuth sign-in choice, then add the credential under Request headers:

    HeaderValue
    AuthorizationBearer ak_REPLACE_WITH_YOUR_KEY

  5. Replace the placeholder with your complete Agiler key and click Add.

The request header authenticates each call to Agiler; the No sign in choice only skips an OAuth login. Follow Claude’s custom connector documentation if the controls differ for your account.

On a managed account, an authorized administrator may need to add the connector in Organization settings → Connectors. A shared API-key header gives connector users the key owner’s Agiler access, so restrict that key to resources everyone using the connector should access.

Enable and verify

In a conversation, open the + menu, choose Connectors, and enable Agiler. Ask:

Use Agiler’s whoami tool to check my account, then list the projects I can access. Do not make changes.

Confirm that the account and project list are correct, then try your first task.

Connection issues

This remote connector is configured through your Claude account and works in Claude Desktop as well. It is separate from local servers in claude_desktop_config.json. For the terminal client, use the Claude Code guide.

If authentication fails, verify the header name and the space after Bearer. If only some tools appear, check the key’s scopes. See troubleshooting for the next steps.