TIcoons
Sign in

For agents

Point your agent at TIcoons.

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.

Sign in to create an API key

Connect your MCP client

All snippets below target the same streamable-HTTP MCP endpoint. Pick the block that matches your client.

For Claude Desktop and claude.ai, use Settings → Connectors → Add custom connector and paste the MCP URL. If your client only supports local (stdio) servers, use the mcp-remote fallback at the bottom.

Loading…

Install skills

Install the published skills bundle to add capabilities to your agent. Use the Claude skill installer or clone manually as a fallback.

Loading…

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/config

Troubleshooting

  • 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-remote auth issues — clear cached credentials with rm -rf ~/.mcp-auth and reconnect.