MCP

Open Tools & MCP

1. Open Cursor.
2. Go to Cursor Settings (Cmd + , on macOS, Ctrl + , on Windows and Linux).
3. Open Tools & MCP.

Add the hosted server

1. Choose Add a new global MCP server (or New MCP server).
2. Select a remote / HTTP / URL server, not a local command.
3. Set the server URL to:

https://boarbs.com/api/mcp

4. Save. Cursor should prompt for OAuth.
5. Sign in to Boarbs and approve access. Choose read-write only if the agent must change data.

Or use an API key in .cursor/mcp.json

Create or edit .cursor/mcp.json in your project (or ~/.cursor/mcp.json for a user-wide server):

{
  "mcpServers": {
    "boarbs": {
      "url": "https://boarbs.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_BOARBS_API_KEY"
      }
    }
  }
}

Replace YOUR_BOARBS_API_KEY with the key from Settings → API. Keep this file out of git if it contains a real key (add it to .gitignore, or use a secret manager). After saving, return to Tools & MCP and confirm the boarbs server is enabled.

Verify the connection

In Cursor chat, ask something like “List my Boarbs boards” and include organizationId when prompted. If tools do not appear, toggle the server off and on in Tools & MCP, or restart Cursor.

Open connector settings

1. Open claude.ai and sign in.
2. Go to Settings.
3. Open Connectors (sometimes labeled Integrations).

Add a custom connector

1. Choose Add custom connector (or Add more → custom connector).
2. Name it Boarbs.
3. Paste the server URL:

https://boarbs.com/api/mcp

4. Save the connector.

Complete OAuth

1. When Claude opens the Boarbs authorization screen, sign in.
2. Approve access. Leave it read-only unless the chat must write.
3. Start a new conversation and ask Claude to list boards or posts. Provide organizationId when asked.

Custom connectors can be limited by your Claude plan or organization policy. If you do not see Add custom connector, an admin may need to allow it.

Add the remote HTTP server

Run this in your terminal, not inside an existing claude session:

claude mcp add --transport http boarbs https://boarbs.com/api/mcp

Add --scope user to make it available in every local project:

claude mcp add --transport http --scope user boarbs https://boarbs.com/api/mcp

Sign in with OAuth

1. Start Claude Code in the project.
2. Run /mcp.
3. Select the boarbs server and complete authentication.
4. Sign in to Boarbs in the browser and approve access.

OAuth is read-only by default. Approve read-write when the agent must create or update records.

Or authenticate with an API key

If you cannot use OAuth, pass a Bearer header. Prefer an environment variable over putting the key in the command history:

claude mcp add --transport http boarbs https://boarbs.com/api/mcp \
  --header "Authorization: Bearer ${BOARBS_API_KEY}"

You can also commit a project .mcp.json that reads the key from the environment. Claude Code requires "type": "http" for a URL entry:

{
  "mcpServers": {
    "boarbs": {
      "type": "http",
      "url": "https://boarbs.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${BOARBS_API_KEY}"
      }
    }
  }
}

Export BOARBS_API_KEY in the same shell that starts Claude Code. Do not commit the raw key.

Verify

claude mcp list

The boarbs server should appear. In a Claude Code session, /mcp should show it as connected. Then ask it to list boards for your organizationId.

Enable developer mode

1. Open chatgpt.com and sign in.
2. Go to Settings → Apps & Connectors.
3. Open Advanced (or Advanced settings) and enable developer mode if you are asked to.

MCP custom connectors typically require a paid ChatGPT plan (Plus, Pro, Team, or Enterprise). Workspace admins can disable connectors.

Create the connector

1. Choose Create (or Add connector).
2. Select a custom / MCP connector.
3. Paste the server URL:

https://boarbs.com/api/mcp

4. Choose OAuth as the authentication method.
5. Save.

Authorize and try it

1. Complete the Boarbs sign-in and permission screen.
2. Start a new chat and enable the Boarbs connector if ChatGPT asks you to pick apps.
3. Ask it to list boards or posts and provide organizationId when prompted.

If you do not see Apps & Connectors or custom connectors, your plan or organization policy does not allow them yet.

Point the client at the hosted URL

Use this endpoint:

https://boarbs.com/api/mcp

Transport: Streamable HTTP (sometimes labeled http or streamable-http). Do not configure a local npx / stdio command for the hosted server.

Authenticate

Prefer the client's OAuth / remote authorization flow. If the client only supports a static header, send:

Authorization: Bearer YOUR_BOARBS_API_KEY

Example generic config:

{
  "url": "https://boarbs.com/api/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_BOARBS_API_KEY"
  },
  "transport": "streamable-http"
}

Organization-scoped tools still need organizationId.