MCP Server Connection
Learn how to connect Presso as an MCP server in Claude Code, Claude Desktop, and other MCP-compatible AI clients.
What is MCP?
The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external tools and data sources. Instead of copying data into prompts manually, MCP allows AI clients like Claude Code to call tools on remote servers, fetch real-time data, and take actions on your behalf.
Presso is an MCP server. When you add it to your AI client, the client gains access to a set of tools for querying Shopify, GA4, Google Ads, Meta Ads, and other e-commerce platforms. The AI decides which tools to call based on your natural language requests.
Adding Presso to Claude Code
Claude Code is the primary and recommended client for Presso. To connect, open your terminal and run:
claude mcp add --transport http presso https://mcp.presso.now/mcp
This command does three things:
- Registers a new MCP server named
pressoin your Claude Code configuration. - Sets the transport protocol to HTTP (required for remote MCP servers).
- Points to the Presso MCP endpoint at
https://mcp.presso.now/mcp.
The configuration is saved to your local Claude Code settings and persists across sessions.
Verifying the connection
After adding the server, start a new Claude Code session:
claude
You can verify the connection in a few ways:
- Ask Claude Code directly: Type something like "What Presso tools are available?" and Claude Code will list the tools it can access through the Presso MCP server.
- Try a simple query: Ask "Show me my Shopify shop info" (assuming you've connected Shopify in the Presso dashboard). If you get back your store details, the connection is working.
- Check the MCP server list: Run
claude mcp listin your terminal to see all registered MCP servers.
Connection options
The claude mcp add command supports additional flags:
# Add with a custom name
claude mcp add --transport http my-presso https://mcp.presso.now/mcp
# Add to project scope (shared with team via .mcp.json)
claude mcp add --transport http --scope project presso https://mcp.presso.now/mcp
| Flag | Description |
|---|---|
--transport http | Required. Specifies the HTTP transport for remote servers. |
--scope user | Default. Saves to your personal Claude Code config. |
--scope project | Saves to the project's .mcp.json file, shareable with your team. |
Claude Desktop setup
Claude Desktop uses a JSON configuration file instead of CLI commands. To add Presso:
- Open Claude Desktop.
- Go to Settings > Developer > Edit Config.
- This opens the
claude_desktop_config.jsonfile. Add Presso to themcpServerssection:
{
"mcpServers": {
"presso": {
"type": "http",
"url": "https://mcp.presso.now/mcp"
}
}
}
- Save the file and restart Claude Desktop.
- You should see Presso listed as an available MCP server. You can now query your connected data sources from Claude Desktop.
Other MCP-compatible clients
Presso works with any client that implements the MCP protocol. The general setup process is the same across clients:
| Client | Configuration method |
|---|---|
| Claude Code (CLI) | claude mcp add --transport http presso https://mcp.presso.now/mcp |
| Claude Desktop | JSON config file (claude_desktop_config.json) |
| ChatGPT | MCP plugin settings (add https://mcp.presso.now/mcp as an HTTP endpoint) |
| Other clients | Consult the client's documentation for adding HTTP MCP servers |
The MCP endpoint is always the same:
https://mcp.presso.now/mcp
Managing MCP servers
Listing servers
To see all MCP servers registered in Claude Code:
claude mcp list
This displays each server's name, transport type, and endpoint URL.
Removing Presso
If you need to remove Presso from Claude Code:
claude mcp remove presso
This removes the server from your configuration. Your Presso account and connected data sources are not affected -- you can re-add the server at any time.
Updating the endpoint
If the Presso endpoint changes (unlikely, but possible), remove and re-add the server:
claude mcp remove presso
claude mcp add --transport http presso https://mcp.presso.now/mcp
How authentication works with MCP
When Claude Code calls a Presso tool for the first time in a session, Presso authenticates your request using the OAuth tokens associated with your Presso account. Here's the flow:
- Claude Code sends a tool call to the Presso MCP endpoint (e.g., "list Shopify products").
- Presso authenticates the session using your account credentials. If this is your first time connecting, you'll be prompted to log in to your Presso account in the browser.
- Presso fetches the data from the connected data source using your stored OAuth tokens.
- Results are returned to Claude Code, which presents them in the conversation.
You don't need to manage API keys or tokens manually. Presso handles authentication transparently.
Connection troubleshooting
"MCP server not found" or connection refused
- Verify the server is registered: run
claude mcp listand check thatpressoappears. - Make sure the endpoint URL is exactly
https://mcp.presso.now/mcp(no trailing slash, no typos). - Check your internet connection. The Presso MCP server requires network access.
"Authentication required" or "Session expired"
- Your Presso session may have expired. Claude Code will typically prompt you to re-authenticate in the browser.
- If you've recently changed your Presso account password, you may need to re-authenticate.
Tools appear but return errors
- Check that you've connected the relevant data source in the Presso dashboard. For example, Shopify tools won't work until you've linked your Shopify store.
- The data source's OAuth token may have expired. Go to the Presso dashboard, disconnect the data source, and reconnect it.
Claude Code doesn't recognize Presso tools
- Restart Claude Code (
Ctrl+Cand runclaudeagain). MCP servers are loaded at startup. - Verify the server is correctly registered with
claude mcp list. - Make sure you're using a recent version of Claude Code that supports HTTP MCP transport.
Slow responses
- Large data queries (e.g., listing thousands of orders) may take longer. Try narrowing your request with filters or date ranges.
- Network latency between your machine and the Presso server can vary. This is normal for remote MCP servers.
Next steps
- Authentication — Understand OAuth flows, token management, and security details.
- Quick Start — If you haven't set up your Presso account yet, start here.
- Basic Usage — Learn effective querying patterns and best practices.