Your Pinkk research, in the chatbot you already use.

Bring your reports, profiles, and comparisons into your existing conversations. Copy a setup prompt and let your AI help you connect.

Get the setup prompt

Eight tools. Only read access. No Pinkk credit charges.

Your research, connected

Ask your chatbot
“Summarise my latest Pinkk report with its sources.”
Pinkk MCP
Your token. Your selected permissions. Your account or team.
Read the evidence
Published findings, source links, and confidence levels.

Ask your AI about your Pinkk research.

MCP (Model Context Protocol) connects a compatible chatbot to your existing Pinkk data. Ask it to summarise reports with sources, explore profiles, or explain comparisons. You choose what it can read; it cannot edit data, run analyses, or spend Pinkk credits.

Try asking: “Summarise my latest Pinkk report with its sources and confidence levels.”

Start with your AI

Connect with a copy and paste.

Copy the prompt and send it to your chatbot. Your AI checks compatibility and guides you through connecting your Pinkk account. Your Pinkk plan must include API access.

With OAuth, you sign in to Pinkk and approve read access. Your chatbot handles the credentials; you do not need to copy a token.

Your setup prompt

Help me connect my Pinkk research to this AI using Pinkk MCP. Use plain language and guide me one step at a time.

Connection details:
- Server URL: https://trypinkk.com/api/mcp
- Transport: remote Streamable HTTP
- Authentication: OAuth authorization code with S256 PKCE and automatic dynamic client registration (DCR); public client, no client secret
- Setup guide: https://trypinkk.com/mcp
- Manage or revoke connections: https://trypinkk.com/api-access

Before asking me to sign in or create a token, identify my chatbot or framework and verify its actual MCP authentication options and whether this account can add custom MCP connections. Check current official documentation or ask what settings I see; do not infer access from a subscription tier or invent controls.

Use OAuth authorization for ChatGPT and other clients that support it. Ask me to add the server URL in the client's custom MCP settings and choose OAuth, not No authentication. Use automatic registration (DCR); do not ask for a manually created Pinkk token, client ID, or client secret. Pinkk publishes protected-resource and authorization-server discovery metadata. If the client requires manual client credentials or cannot use DCR, explain that limitation rather than inventing credentials. A Tunnel tab is not needed for Pinkk's public server.

If you have authorized configuration tools, help configure the connector using those tools, requesting any necessary approval. Otherwise, explain exactly which connector settings I should open and what to enter. Only after confirming compatibility, have me sign in to Pinkk in the authorization window and check that my plan includes API access. On the consent page start with only read:analyses for reports; offline_access permits refresh for up to 30 days. Explain what data my AI provider will receive. Only suggest read:profiles, read:comparisons, or read:workspaces if I want those categories too; never request write scopes.

Never ask me to paste my token or password into this chat. OAuth exchanges credentials automatically after I approve access. If my framework only supports manually stored bearer tokens, first verify a secure credential field exists; then guide me to create a dedicated, expiring token with only read:analyses at https://trypinkk.com/api-access and enter it in that field. Do not place credentials in URLs or committed files.

After setup, use the actual MCP connection to discover tools and call list_reports. Only confirm success after a real tool response; an empty list is valid. If unavailable, say setup is unverified and help resolve it. Then ask which completed report I want to discuss. These tools read existing data and cannot run analyses or spend Pinkk credits.

Paste the prompt into your chatbot, then sign in to Pinkk when the connection asks you to approve access.

Prefer manual setup?

Add the server URL below in your chatbot's remote MCP settings. Choose OAuth and automatic client registration; leave optional client ID and client secret fields empty.
Sign in to Pinkk and approve the read permissions. Start with reports; select other categories only if you need them.
Enable the connection and ask your AI to list your Pinkk reports. A real tool response confirms that it is connected.

Server URL

https://trypinkk.com/api/mcp

Transport: Streamable HTTP
Authentication: OAuth (recommended) or bearer token

For frameworks using API tokens

If your framework uses bearer tokens or custom headers, create a dedicated, expiring token in Pinkk API access with read:analyses. Optional scopes are read:profiles, read:comparisons, and read:workspaces. Set the header below in its secure credential configuration. Do not put a token in a chat or the server URL.

Authorization: Bearer YOUR_PINKK_TOKEN

Use a server or desktop MCP client. Browser clients on another website are rejected by Pinkk's Origin checks. Local stdio and legacy HTTP/SSE transports are not provided.

FAQ

Quick answers about connecting, permissions, and your data.

No. Your client must support remote MCP over Streamable HTTP with OAuth, or securely stored bearer tokens. Check that your account can add a custom MCP connection; availability depends on the chatbot and its account settings.

Use the OAuth sign in flow in ChatGPT’s custom MCP settings. Add the Pinkk server URL, choose OAuth, then sign in to Pinkk and approve the read permissions. Your ChatGPT account must allow custom MCP connections. Confirm the connection with a real Pinkk tool response.

Automatic configuration depends on your chatbot’s tools and permissions. The prompt asks your AI to check what it can do, then either help configure the connection or guide you through the settings. You sign in to Pinkk and approve access yourself. With OAuth, your chatbot receives its credentials securely; there is no token to paste into the chat.

There is no separate MCP entitlement. Your Pinkk plan must include API access. The same account access rules apply, and MCP has its own request limit.

No Pinkk credits are charged for these tools. They read existing data and cannot run new analyses. Your chatbot provider may charge for its own usage.

Only the data allowed by your token scopes and your account or current team permissions: profiles, published analysis reports, comparisons, and workspace membership. Private Research Hub evidence and workspace intelligence report bodies are not included in this version.

No. All eight MCP tools only read data. They cannot edit profiles, submit analyses, create workspaces, or spend credits, even if your token also has write scopes. Use a dedicated token with only the read scopes you need.

Your chatbot provider receives the data retrieved through the connection. Review that provider's data handling settings and terms before connecting. Token scopes select categories of data, not individual reports or profiles.

Check that your client supports the connection, your plan includes API access, and your token has the right read scopes and has not expired. Reports must be published and belong to your account or team. If you reach the rate limit, wait before retrying.

Revoke the connection’s MCP token in Pinkk API access and remove the connector from your chatbot. Expired tokens also stop working. Revocation stops future requests; it does not erase data already retrieved by your chatbot.

Need more help? Contact Pinkk or read the API reference.