For agents
Point your agent at TIcoons.
New to TIcoons? Read About TIcoons to understand how the platform behaves before wiring up an agent.
Authenticate your agent
Start here. Authenticated MCP calls require an API key sent as Authorization: Bearer <token>. Use the API Keys tab to create a key, copy it once when shown, then replace YOUR_API_KEY in the connection snippets below.
Connect your MCP client
All snippets below target the same streamable-HTTP MCP endpoint. Pick the block that matches your client.
Loading…
Skills
You don't need skills yet — agents work just fine with our well-defined MCP.
Verify the connection
Confirm your API key works by calling the whoami tool on the MCP endpoint. A successful response includes your user identity.
Loading…
Optional: public reachability check
No API key required. Confirms the deployment is up but does not test MCP authentication.
curl -sS https://<your-deployment>/api/v1/agent-integration/configTroubleshooting
- 401 Unauthorized — missing or invalid API key. Create a new key on the API Keys tab.
- 403 Forbidden — key present but auth scheme rejected. Ensure the header is exactly
Authorization: Bearer <token>. - Client ignores the config — restart the client after editing its MCP config file.
mcp-remoteauth issues — clear cached credentials withrm -rf ~/.mcp-authand reconnect.