Guides

Connect Pineprompt to your AI tools over MCP

Pineprompt hosts a remote MCP server, so you may connect an AI assistant such as Claude or ChatGPT straight to your account and ask it about your data in plain language. MCP, the Model Context Protocol, is the open standard that lets an assistant work with outside tools. There is nothing to install and no key to manage: you connect with one address and sign in once in your browser.

The endpoint

The server is remote and hosted. Every client connects to the same address:

https://pineprompt.com/mcp

That is the only address you need. Each client section below shows where to paste it.

Before you begin

You will need a Pineprompt account that belongs to at least one organization. The MCP server is included on every plan, so you may connect right away.

Signing in

The first time a client connects, it opens a Pineprompt window in your browser. You sign in, approve access, and the connection is remembered, so you are not asked again.

The connection acts as you, not as an organization. It may reach every organization you belong to, and in each one it may do whatever your role allows. Each tool takes an organization, and often a project, to choose what it acts on.

Claude

Custom connectors work on every Claude plan, including Free, though Free allows only one and the feature is in beta. You add Pineprompt once, and it follows your account across claude.ai, Claude Desktop, and mobile.

  1. Open Customize → Connectors. Some Claude menus label this Settings → Connectors.
  2. Click the + next to Connectors, then choose Add custom connector.
  3. Enter a name and the server URL, https://pineprompt.com/mcp. You may leave the optional Advanced settings empty.
  4. Click Add.
  5. A Pineprompt window opens in your browser. Sign in and approve access, and Claude returns connected.
  6. To use it in a conversation, click the + in the message box, choose Connectors, and turn Pineprompt on.

Claude Desktop uses the same Connectors panel, so you add Pineprompt exactly as above.

On Team and Enterprise, an Owner adds the connector once under Organization settings. Each member then opens their own Connectors page, clicks Connect, and signs in under their own account, so Claude only reaches what that member can see.

ChatGPT

ChatGPT connects through Developer mode, on the web only; the Free plan cannot use it. Business, Enterprise, and Edu workspaces can run Pineprompt's full read and write tools. Pro is limited to read-only tools, and availability on Plus is still changing, so you should check your own settings. OpenAI now labels this area Apps, where older guides say Connectors.

  1. On ChatGPT for web, open Settings → Apps → Advanced settings and turn on Developer mode. On Business, Enterprise, and Edu, an administrator enables this first.
  2. Under Settings → Apps, click Create. The control appears only once Developer mode is on.
  3. Enter a name, the URL https://pineprompt.com/mcp, and choose OAuth.
  4. Click Scan tools. Sign in to Pineprompt when prompted and approve access.
  5. Click Create. Pineprompt now appears under Settings → Apps.
  6. To use it, open a chat and pick Pineprompt from the tools menu, or name it in your prompt.

Read tools run on request; write tools ask you to confirm, and they work only on Business, Enterprise, and Edu. This is a beta surface, so the menu labels above may change.

Any other client

Claude and ChatGPT connect on their own. Other clients, and some older versions, need a small bridge called mcp-remote: it runs locally through npx, connects to Pineprompt, and opens your browser to sign in. It needs Node.js 18 or higher and nothing to install.

Add this to your client's MCP configuration:

{
    "mcpServers": {
        "pineprompt": {
            "command": "npx",
            "args": ["-y", "mcp-remote@latest", "https://pineprompt.com/mcp"]
        }
    }
}
  • The file lives in a different place per client; for example, Cursor reads ~/.cursor/mcp.json. Visual Studio Code uses a servers key instead of mcpServers.
  • Save the file and restart the client. The first launch opens your browser to sign in; after that it stays connected.
  • You should keep mcp-remote@latest, as shown, to stay on a patched version.

What you can ask for

The server mirrors what you can do in the dashboard. You may work with your organizations, projects, and monitors; your prompts, tags, brands, and segments; and your sources. You may read the AI responses each monitor produces, along with the brand mentions and citations within them, and pull visibility, share of voice, and sentiment as time series.

For example, you might ask your assistant to list your monitors, create a prompt, read this week's responses, or chart your share of voice against a competitor.

For the exact inputs and outputs behind any tool, see the API reference.

Troubleshooting

Tool calls fail right after you connect.
The browser sign-in did not finish. Re-open the connector, sign in, and approve access before asking for a tool.
mcp-remote loops on sign-in, or returns a token error.
Clear its cached login with rm -rf ~/.mcp-auth, then restart the client.
Claude Desktop does not show Pineprompt.
Add it through the Connectors panel, the same as on the web, then fully quit and reopen Claude Desktop. Closing the window is not enough.
ChatGPT is missing the write tools.
Write tools need a Business, Enterprise, or Edu workspace. If they still do not appear, open the app under Settings → Apps and refresh it.
You cannot find Add custom connector in Claude, or Create in ChatGPT.
In ChatGPT, turn on Developer mode, and check the plan is not Free. In Claude on Team or Enterprise, an Owner must add the connector before members can connect.
A tool says it cannot act in an organization.
Your role in that organization does not allow the action. Use an account whose role does, or name an organization where you hold it.

A note on security

When you add Pineprompt, Claude and ChatGPT will note that custom connectors are third-party services they have not verified. That is expected. A few habits keep things safe.

  • Connect with an account whose role matches what you want the assistant to reach.
  • Approve write actions one at a time rather than allowing them all at once.
  • Disconnect the connector at any time to revoke its access.