Claude connector setup

Gyrence is available as an OAuth-connected MCP server in the Lovable agent catalog. This lets Claude (and other MCP clients) connect as your signed-in Gyrence user rather than requiring a workspace API key.

Use this page when you are adding Gyrence to Claude via the Lovable → Agent integrations flow.

Required URLs

How to connect

1. In Claude, go to Settings → Connectors and choose Add custom connector.
2. Paste the MCP server URL: https://www.gyrence.com/lovable-mcp.
3. Claude fetches the OAuth resource metadata and opens the Gyrence consent screen.
4. Sign in with your Gyrence Google account.
5. Click Approve on the consent screen.
6. Claude can now call whoami, list_blog_posts, upsert_blog_post, and upsert_release_note.

Important notes

• Use https://www.gyrence.com/lovable-mcp, not https://gyrence.com/lovable-mcp. The apex redirects to www and some MCP clients do not follow redirects.
• The OAuth server supports dynamic client registration, so no manual Client ID or Secret is required.
• The OAuth server exposes identity and content tools: whoami, list_blog_posts, upsert_blog_post (writes Markdown to public.blog_posts.content_md), and upsert_release_note (writes Markdown to public.release_notes.body_md). Content writes run as the signed-in user and require the Gyrence admin role. The five Gyrence data primitives are served by the workspace-key endpoint at /api/mcp.
• The consent screen is at /.lovable/oauth/consent. If you are sent to the login page first, sign in and you will be redirected back to consent automatically.

Adding the retrieval primitives (second connector)

The five primitives (search, fetch, gyre, extract, map) are not on the OAuth connector. They live on a separate MCP server that authenticates with a workspace API key. Add it as its own custom connector:

1. Create a workspace key at https://www.gyrence.com/app/api-keys (keys start with mc_).
2. In Claude, Settings → Connectors → Add custom connector.
3. Server URL: https://www.gyrence.com/api/mcp (full URL — a bare /api/mcp path will not resolve).
4. Auth: bearer token — paste the mc_… key as the credential. Claude sends Authorization: Bearer mc_….

A machine-readable descriptor of this endpoint (auth schemes, tool names) is served at https://www.gyrence.com/.well-known/mcp.json.

Troubleshooting

If Claude reports "this session can't run that flow itself", you are using the claude_desktop_config.json transport, which does not support OAuth. You must add Gyrence through Claude's in-app connector settings instead.