# Connect an AI assistant with MCP > Configure a remote MCP client, sign in with OAuth and verify access without embedding an admin key. Canonical URL: https://pollenate.dev/docs/integrations/mcp-setup/ ## Server address ```text https://api.pollenate.dev/mcp ``` Pollenate exposes a remote Streamable HTTP MCP server. Configure it as an HTTP server in your client, then complete Pollenate's OAuth sign-in and consent screen. Choose the intended organization and review the requested scopes. Your assistant acts within your account's permissions. The client must support remote MCP and the selected authentication method. Workspace policy can restrict adding custom servers; check your client administrator's settings if connection controls are unavailable. ## Claude Code ```bash claude mcp add --transport http pollenate https://api.pollenate.dev/mcp ``` Run `/mcp` inside Claude Code and authenticate Pollenate. See the [official Claude Code MCP instructions](https://code.claude.com/docs/en/mcp) for client-specific options. ## VS Code Add a remote server to `.vscode/mcp.json`: ```json { "servers": { "pollenate": { "type": "http", "url": "https://api.pollenate.dev/mcp" } } } ``` Start the server and complete sign-in. Refer to [VS Code's MCP documentation](https://code.visualstudio.com/docs/agent-customization/mcp-servers) for trust controls and client configuration. Other clients use the same server URL. Prefer their native OAuth connection rather than putting a privileged organization key into a shared project file. ## Personal-key fallback For a client that can send a header but cannot complete OAuth, create a personal key in Profile. Use `read` for supported read workflows and add `write` only when you need to build or edit forms. ```http Authorization: Bearer pk_user_YOUR_PERSONAL_KEY ``` This is a credential placeholder, not a working key. Store the real value in the client's secret/credential facility. An organization key is a separate option for server automation and acts as the organization, not as the person running the client. ## Verify the connection 1. Ask the assistant to list accessible brands or inboxes. 2. Ask it to draft a small form in the selected brand. 3. Read the draft before publishing it. 4. Publish only after reviewing the questions and sharing settings. 5. Submit a test response yourself, then ask the assistant to read it. Use the exact [tool names](/docs/integrations/mcp-tools/) if the assistant needs guidance. The available tools do not include a form-deletion tool. A 401 with `WWW-Authenticate` asks the client to sign in or refresh an expired/revoked token. A 403 or tool permission error means scope, membership, brand access or ownership needs attention. A 503 credential lookup error is temporary; retry later instead of repeatedly discarding valid credentials. Pollenate also publishes [skill.md](https://pollenate.dev/skill.md) for agent discovery. Treat source-reviewed docs and current tool schemas as the detailed contract, especially for credential differences.