Connect MCP server
Every server in the MCPs catalog (and any external tool that exposes an MCP server) connects through the same wizard. The process has three steps: Connection → Select tools → Done.
You can reach this wizard from two places, and the result is the same:
- The main Integrations page — by clicking one of the catalog cards (Shopify, Notion, GitHub…), which open the wizard with their ready-made preset.
- Functions → MCPs — from the Quick connectors (the same presets) or with "New MCP" for any other server.
You can start from a preset (which preloads most of the configuration) or use "Other provider" to configure the connection manually.
Platica only supports the Streamable HTTP transport. The Stdio transport doesn't apply to web connections.
Step 1: Connection
Option A: Use a catalog preset
When you pick a featured app (for example, Shopify), the wizard preloads the name, description, and MCP server URL, and shows you a "How it connects" box with that provider's specific instructions.
For Shopify you only need to fill in your store subdomain (what appears before .myshopify.com); the server URL is built automatically from that.
Always read the "How it connects" box. Its instructions change per provider: Shopify asks for the subdomain, Browserbase concatenates your API key into the URL, Exa works with no auth on its free tier, and GitHub requires registering your own OAuth App. You'll also find links to each service's official documentation there.
Some presets, like Zapier, don't come with a fixed URL: each user creates their own MCP server at mcp.zapier.com (choosing which apps and actions it exposes), copies the personal URL Zapier generates, and pastes it into the "Your Zapier MCP server URL" field. In these cases the authentication is No auth, because the URL itself acts as the credential.
Option B: Other provider
If the tool you want isn't in the catalog, click "Other provider" (top-right corner) to configure the connection manually.
Connection fields
| Field | Description |
|---|---|
| Name | How you'll identify this integration within Platica. |
| Description | A short note about what the integration is for (optional). |
| MCP server URL | The address of the MCP server you'll connect to. Presets fill it in for you; with "Other provider" you enter it manually. |
| Authentication | The method Platica uses to authenticate with the server. |
| Additional headers | Extra HTTP headers the server may require (optional). |
Authentication methods
The right method depends on each server; the preset's "How it connects" box tells you which one to use.
| Method | When to use it |
|---|---|
| No auth | The server is public or offers a free tier with no credentials (for example, Shopify's Storefront MCP or Exa on its free tier). |
| Bearer | The server expects a bearer token. Useful for a Personal Access Token (for example, on GitHub). |
| API Key | The server authenticates with an API key. When you pick it, you can set the header name and an optional prefix (for example, Authorization + Bearer, or a custom header like x-api-key). Some servers embed the key directly in the URL (like Browserbase). |
| OAuth 2.0 | The server uses the OAuth 2.0 authorization flow (common in Notion, Linear, or HubSpot). |
OAuth 2.0 connections: a window will open after you install so you can authorize access to your account.
- If the server supports Dynamic Client Registration (like Notion or Linear), client registration is automatic and you don't need a
client_idorclient_secret. - If it doesn't (like GitHub, HubSpot, Asana, or Salesforce), you'll need to register your own OAuth App and paste your
client_idandclient_secretin the "Advanced" section, using the Authorization callback URL (or redirect URL) that Platica shows in the "How it connects" box.
Advanced configuration
Some servers need extra data that appears when you expand the "Advanced" section:
| Field | What it's for |
|---|---|
| Scope | Limits the permissions the authorization will request (optional). |
| Client ID / Client Secret | Credentials for your own OAuth App, required when the server doesn't support Dynamic Client Registration (GitHub, HubSpot, Asana, Salesforce…). |
In addition, some servers adjust their scope through URL parameters or an extra header:
- Supabase accepts
?project_ref=<your-ref>or?read_only=trueat the end of the URL to narrow access. - Wix requires an extra
wix-account-idheader with your Account ID.
When connecting servers that touch sensitive data (like databases), use development environments and narrow the scope with scopes or parameters like read_only. Avoid connecting your agent directly to a production database.
When you've filled in the details, click "Connect and discover".
Step 2: Select tools
Platica connects to the MCP server and automatically discovers the tools it exposes. You'll see how many it found along with the server's identity (name, version, protocol, and transport).
Each tool appears with its name and a short description of what it does. They all come checked by default; the ones you leave selected will be installed in your workspace. For example, the Shopify server exposes:
| Tool | What it does |
|---|---|
search_catalog | Searches for products from the online store. |
get_cart | Gets a cart (items, shipping, discounts, and checkout URL). |
update_cart | Updates a cart: add or remove items, buyer info, shipping, discount codes, etc. |
search_shop_policies_and_faqs | Looks up the store's policies, products, or services. |
get_product_details | Gets a product's details by its ID. |
Once you've made your selection, click "Install N tools".
Install only the tools your agent actually needs. The narrower the list, the easier it is for the agent to pick the right tool at the right moment.
Step 3: Done
The integration is installed and its tools available in your workspace.
From here you can "Back to list" or go to "View details" of the server you just connected.
Connecting the server makes the tools available at the workspace level, but it doesn't activate them on its own. Each agent activates the tools it wants to use from its own "Tools" tab.
Manage a connected server
Clicking a server from the list opens its detail view, where you can monitor and manage the connection.
Connection information:
| Field | Description |
|---|---|
| URL | The MCP server's address. |
| Auth | The configured authentication method (No auth, Bearer, API Key, or OAuth 2.0). |
| Config ID | Internal identifier for this configuration. |
| Transport | The transport used (Streamable HTTP). |
| Server | Name and version of the MCP server. |
| Last sync | Date and time Platica last synced the tools. |
Other sections of the view:
- Statistics — Tool call activity over the last 24 hours, 7 days, or 30 days.
- Tools — Which tools you have installed out of those the server exposes.
- Logs — A record of the server's activity.
From this screen you can also Refresh the connection (to rediscover and resync the tools if the server changed) or Delete the integration entirely.