# Connect your assistant

Set up a compatible remote MCP client with your MARqentic workspace.

## Before connecting

Use Google or enter your email on the sign-in page, then verify the six-digit code sent to your inbox. No password is needed. A new workspace begins with zero research credits. Free estimates are available before you fund paid research.

Use the MCP URL below in a client supporting remote Streamable HTTP and the advertised OAuth flow.

```
https://devshine-seo-mcp.vercel.app/mcp
```

- [Connect Claude](/docs/clients/claude)
- [Connect Claude Code](/docs/clients/claude-code)
- [Connect ChatGPT](/docs/clients/chatgpt)
- [Connect Codex](/docs/clients/codex)
- [Connect Cursor](/docs/clients/cursor)
- [Connect Gemini CLI](/docs/clients/gemini)
- [Connect Grok](/docs/clients/grok)
- [Connect Grok Bot](/docs/clients/grok-bot)
- [Connect OpenCode](/docs/clients/opencode)
- [Connect Any other MCP client](/docs/clients/other)

## Claude, ChatGPT and other remote clients

In the assistant’s connector settings, add the MARqentic MCP URL. Complete the browser authorization, check the callback origin and select the intended workspace. Approve only a connection you started.

For Cursor or a client using a custom Authorization header, create a key under Settings → API keys. Keep its secret outside source control and revoke it when it is no longer needed.

1. Add a remote MCP server, using the canonical URL.
2. Sign in and review the requested access.
3. Choose a workspace and explicitly approve.
4. Ask the assistant to list the available tools, then request a dry-run quote.

## If a connection fails

Check that the deployment uses HTTPS, that the complete URL ends in /mcp and that the client supports the advertised registration/resource flow. A successful local test does not verify a vendor’s production connector approval.

Review Connections to revoke old grants. Disabled categories may require refreshing your assistant’s cached tool list.