How to Connect MCP Servers in Vincony: A Step-by-Step Setup Walkthrough

# How to Connect MCP Servers in Vincony: A Step-by-Step Setup Walkthrough

MCP (Model Context Protocol) is the open standard that lets your Vincony agents reach out and do things — query a database, post to Slack, read from GitHub, update a CRM — without you writing a line of integration code. If you've read the conceptual overview, you already know the "why." This post is the "how": a concrete, click-by-click walkthrough of the MCP Connections panel inside Vincony OS.

How MCP Works Inside Vincony

Vincony's MCP layer is powered by Composio, a managed toolkit router. Instead of hosting your own MCP server, Vincony creates a router session on your behalf — a persistent, addressable MCP endpoint that lives in the cloud. That session acts as a proxy: it holds the authentication tokens for whichever tools you've linked, and it exposes all of them to any MCP-compatible AI client through a single server URL.

The three core concepts to keep in mind:

• Router session — a persistent MCP server URL scoped to your account. You can have multiple sessions, each grouping a different set of tools.
• Toolkit — a named integration (gmail, slack, github, notion, etc.). You attach one or more toolkits to a session.
• MCP Server URL — the address your AI client (Claude Desktop, a custom agent, Vincony's own Agents workspace) connects to.

When an agent invokes a tool through MCP, the router session handles authentication, rate-limiting, and audit logging automatically — scoped access by default, with encryption in transit.

Before You Start

You need a Vincony account. MCP Connections is available on all plans, though the number of active sessions and linked toolkits you can maintain scales with your plan. Free and Starter accounts are great for experimenting; Pro, Power, and Business unlock higher session limits and team-level sharing. Check pricing to see what fits your workflow.

Step-by-Step: Creating Your First Router Session

Step 1 — Open MCP Connections

Log in and navigate to MCP Connections in the left sidebar under the OS section. You'll land on the MCP Connections panel, which shows the "What is MCP?" overview cards at the top and the Router Sessions manager below.

Step 2 — Enter Your Toolkits

In the Router Sessions card you'll see a text input labeled "Toolkits (comma separated, e.g. gmail, slack)". Type the slug names of the tools you want this session to serve. Toolkit slugs match the service names you'd expect — gmail, slack, github, notion, linear, googlecalendar, postgres, and dozens more are available through Composio.

You can bundle multiple toolkits in one session. For example, to create an email-and-calendar session, type gmail, googlecalendar in the field. For a dev-workflow session, try github, linear, slack.

Tip: start small. A session with two or three tightly-related toolkits is easier to reason about than one giant session with everything in it.

Step 3 — Create the Session

Click the Create button (or press Enter). Vincony calls the Composio router API and provisions your session. After a moment you'll see a confirmation toast and the new session appears in the list below, showing:

• The session ID (a short alphanumeric string)
• The toolkit badges you specified
• The creation timestamp

The session is now live. At this point it exists but the individual toolkits aren't authenticated yet — that's the next step.

Step 4 — Inspect the Session and Grab the MCP URL

Click the eye icon on the session row to expand the detail panel. Two things appear:

MCP Server URL — this is the address you'll paste into any MCP-compatible client. Copy it with the copy button next to the URL. Keep it safe; anyone with this URL can connect to your session.

Linked Toolkits — a list of the toolkits you specified, each showing a status badge: Connected (authenticated) or Not linked (needs OAuth/auth). Brand-new sessions will show "Not linked" for every toolkit until you authorize them.

Step 5 — Link (Authenticate) Each Toolkit

Still inside the expanded detail panel, find the "Toolkit to link..." input at the bottom. Type a toolkit slug — for example gmail — and click the Link button. Vincony will redirect you through Composio's OAuth flow for that service.

What happens next depends on the toolkit:

• OAuth-based services (Gmail, Slack, GitHub, Google Calendar, Notion) — you'll be taken to that service's standard authorization screen. Grant the requested permissions and you'll be redirected back to MCP Connections automatically. The toolkit badge updates to Connected.
• API-key-based services — you'll be prompted to paste your API key or connection string. These are encrypted at rest and never exposed in plain text after entry.

Repeat this for each toolkit in the session. Once all badges show Connected, the session is fully operational.

Step 6 — Connect Your AI Client

Now use the MCP Server URL you copied in Step 4. The exact integration point depends on which client you're wiring up:

Claude Desktop — Open the configuration file for Claude Desktop (typically claude_desktop_config.json in your AppData or Application Support folder) and add an entry under the mcpServers key. Set command to the transport type (usually sse or streamable-http) and url to your MCP Server URL.

Vincony Agents — Head to Agents, open or create an agent, and look for the MCP / Tools section. Paste the MCP Server URL and save. The agent will automatically discover the available tools from the session and can use them in any conversation or automated run.

Custom API clients — If you're building your own agent with the Claude API, OpenAI Agents SDK, or another framework, initialize an MCP client pointing at the session URL. The session speaks standard JSON-RPC 2.0 over SSE or HTTP streaming, so any spec-compliant client works.

Step 7 — Test the Connection

Back in Agents, open a test conversation and ask the agent to do something that exercises the linked toolkit. For a Gmail session, try: "Check my inbox and summarize the three most recent emails." For a GitHub session: "List the open pull requests in my main repository."

If the agent responds with real data, your MCP session is working correctly. If it says it can't access the tool, go back to the detail panel in MCP Connections and verify all toolkit badges show Connected.

Managing Multiple Sessions

You can create as many sessions as your plan allows. Common patterns:

• One session per agent — keeps tool access narrow and auditable
• One session per team function — a "marketing" session (gmail, notion, slack) and a "engineering" session (github, linear, postgres) shared across the relevant agents
• Throwaway test sessions — create a session for a quick experiment, then delete it with the trash icon once done

Session IDs are stored in your browser's local storage and in Vincony's backend. The copy-ID button on each row makes it easy to reference a session ID in agent configs or scripts.

Tips and Troubleshooting

Toolkit shows "Not linked" after OAuth — This sometimes happens if the redirect was blocked or the browser tab closed early. Click the eye icon to open the detail panel, then use the Link input to re-run the auth flow for that specific toolkit.

MCP Server URL returns 401 — The session may have been revoked or the Composio token expired. Delete the session and create a fresh one, then re-link the toolkits.

Agent can see the session but doesn't call tools — Check that the agent's system prompt or instructions mention the available tools. Some model configurations require explicit permission grants before tool use is enabled.

Want to add a toolkit after the session is created — You don't need to recreate the session. Expand the detail panel, type the new toolkit slug in the Link input, and authorize it. The new tool appears in the same session's capability list immediately.

Session list is empty after clearing browser data — Session metadata is stored in local storage as a convenience cache. The sessions still exist on Composio's backend. You can recover them by recreating sessions with the same toolkit slugs — the underlying auth for already-connected services persists on the Composio side.

What to Do Next

With a live MCP session you've unlocked the most powerful dimension of Vincony's agent platform: agents that don't just reason, but act. A few directions worth exploring:

• Build a multi-step agent in Agents that chains MCP tool calls — for example, one that reads a GitHub issue, checks a Linear sprint, and drafts a Slack update automatically.
• Connect external data sources via Connected Apps to complement your MCP toolkits with Vincony's native integrations.
• Explore the API at /docs/api if you want to provision and manage sessions programmatically as part of a larger pipeline.

MCP turns Vincony from a smart conversation interface into an agent that can reach every tool in your stack. The setup takes under ten minutes — the workflows you build with it can save hours every week.