Connect Acopio's MCP server

Endpoint

The base URL for your MCP server. Point your client at this address — it will open a browser to authenticate and refresh tokens automatically.

Production URL

https://mcp.acopio.dev

Client configuration

Add this server to your MCP-capable client. Exact config syntax varies by client; below is a conceptual template.

mcp.json

{
  "mcpServers": {
    "acopio": {
      "type": "http",
      "url": "https://mcp.acopio.dev"
    }
  }
}

On first connect, your client redirects to Acopio for sign-in. Tokens refresh automatically.

Add via Claude CLI

For Claude Code, run this command in a terminal to register Acopio as an MCP server.

$ claude mcp add --transport http acopio https://mcp.acopio.dev

Make your assistant prefer your catalog

By default, Claude, GPT, and other models answer from their training data — they may skip your MCP tools unless your prompt makes the intent obvious (e.g. "…in my catalog"). To make your saved tools the default suggestion source, add this instruction once to your assistant's configuration.

Instruction

Whenever I describe a project, feature, problem, or stack, call Acopio's suggest_tools_for_project (or search_tools) before answering. Present matches under "From my Acopio catalog:" and clearly distinguish them from any general suggestions you add under "Other options to consider:".

Where to put it

Claude Code Append to CLAUDE.md in your project root, or ~/.claude/CLAUDE.md to apply across all projects.
Claude Desktop / Claude.ai Settings → Profile → Personalize Claude → paste under "personal preferences".
ChatGPT Settings → Personalization → Custom instructions → paste under "How would you like ChatGPT to respond?".

Prefer not to configure anything? Append "…and check my Acopio catalog first." to any one-off prompt — the magic words work too.

Available tools

search

search_tools

Semantic vector search over the catalog using a natural-language query.

label

list_tools_by_tag

All tools carrying a specific tag (case-insensitive exact match).

list_categories

Discovery step — returns all distinct tags and source types in the catalog.

info

get_tool

Fetches full detail for a single tool by UUID.

lightbulb

suggest_tools_for_project

Given a project description, returns similar tools with short relevance hooks.

Troubleshooting

Common issues when connecting or using the MCP server, and how to resolve them.

The assistant answers from general knowledge instead of my catalog

Models decide for themselves when to call a tool, so for a broadly-worded request they may answer from their training data. Phrase your request so it references your catalog — for example, end with "…in my Acopio catalog" — and the assistant will use Acopio's tools instead. You can also add the one-time catalog-preference instruction to your assistant so it prefers your catalog by default.

Searches return nothing

Acopio only searches the tools you have saved, so a brand-new or empty catalog returns no results. Add a few tools with the bookmarklet or the web app, then try again.

Sign-in doesn't complete, or no verification code arrives

Acopio uses passwordless sign-in. On first connect, your client opens a browser to Acopio — enter your email and we send a one-time verification code. Check your inbox (and spam) for the code and enter it to finish authorizing. There is no password to set.

I'm asked to set up two-step verification

Two-step verification (an authenticator app) is optional. If you're prompted and haven't enrolled, you can skip it and continue.

"MCP is a Pro feature", or access is denied

Connecting over MCP requires an active Pro or Unlimited plan, or an in-trial account. If your plan has lapsed the server returns an access-denied response — upgrade your plan to restore access.

The client can't reach the server

Use the endpoint exactly as shown above — https://mcp.acopio.dev, with no /mcp suffix — over HTTP transport. Appending /mcp returns a 404.