---
title: Getting started with MCP1
description: Add your first MCP server, connect Claude Code, Cursor, ChatGPT or any client to your gateway URL, and make your first tool call. About ten minutes.
canonical: https://mcp1.com/blog/getting-started-with-mcp1
last-updated: 2026-11-17
---

# Getting started with MCP1

Add your first MCP server, connect Claude Code, Cursor, ChatGPT or any client to your gateway URL, and make your first tool call. About ten minutes.

![](https://avatars.githubusercontent.com/u/1297371?s=96&v=4)Eldad FuxFounder and CEO, Appwrite

Get startedmcp1.com/mcp/acme/general

1. Add a server
2. Connect a client
3. `deepwiki__ask_question`First call

Get startedmcp1.com/mcp/acme/general

1. Add a server
2. Connect a client
3. `deepwiki__ask_question`First call

This guide takes you from a new account to your first tool call. You’ll add one MCP server, connect one AI client to your gateway URL, and ask your agent to use a tool. It takes about ten minutes.

We use [DeepWiki](https://mcp1.com/servers/deepwiki) as the first server because it needs no account or token, so nothing gets in the way of the first call. Once that works, every other server follows the same steps.

## Before you start

- **An MCP1 account with a verified email.** [Sign up](https://mcp1.com/signup), then open the link in the email we send. You can’t approve a client until your email is verified.
- **An AI client that supports remote MCP servers.** This guide uses Claude Code. Cursor, VS Code, Claude, ChatGPT, Codex, Gemini CLI, Windsurf and OpenCode work too.

## 1\. Create your workspace

After you verify your email, MCP1 asks you to create a workspace. Give it a name, and MCP1 suggests a URL from it. The URL becomes part of every gateway address in the workspace, so a workspace at `acme` gets URLs that start with `https://mcp1.com/mcp/acme`.

Pick the **Individual** plan to start for free. It includes 15 servers and 3 gateways. Then select **Create workspace**.

![The New workspace form, with the name Acme, the URL /mcp/acme and the Individual plan picked.](https://mcp1.com/blog/getting-started-with-mcp1/new-workspace.jpg)

You land on **Get started**, a checklist of setup steps. It ticks each one off as you finish it, so you can come back to it at any time.

## 2\. Add your first MCP server

MCP1 connects your clients to remote MCP servers. You choose which ones from a catalog of 275 servers, or you add your own by URL.

1. 1In your workspace, open **Catalog**.
2. 2Search for **DeepWiki** and select it. Its details show what it can do and that it needs no authentication.
3. 3Select **Install for the workspace**, then **Add and sync**. DeepWiki doesn’t need a token, so there’s nothing else to fill in.

![DeepWiki’s details in the catalog, with the Install for the workspace button.](https://mcp1.com/blog/getting-started-with-mcp1/catalog-deepwiki.jpg)

MCP1 connects to the server and reads its tools. You’ll see a message that DeepWiki is connected, with the number of tools that are ready.

Adding a different server

Servers that support OAuth, like Linear, Notion and Sentry, show a **Connect with** button. Sign in to that service, and MCP1 stores and refreshes the token for you. For a server that isn’t in the catalog, select **Add by URL** and paste its address.

## 3\. Put the server on a gateway

Your clients reach servers through a gateway. Every workspace starts with one, called **General**, which is empty until you add servers to it.

Right after DeepWiki connects, MCP1 asks which gateways should get it. Choose **General** and select **Add to General**.

![The DeepWiki is connected dialog, with the General gateway ticked and the Add to General button.](https://mcp1.com/blog/getting-started-with-mcp1/add-to-general.jpg)

If you skipped that step, open **Servers**, open the server’s menu and choose **Add to a gateway**.

## 4\. Connect your AI client

Select **Connect to MCP1** at the top of the sidebar, or press `C` anywhere in your workspace. The Connect page has two choices:

1. 1Under **Gateway**, pick **General**.
2. 2Under **Your app**, pick your client. The page shows the steps for that client with your real gateway URL filled in.

![The Connect a client page, with the General gateway and Claude Code picked, and the claude mcp add command to copy.](https://mcp1.com/blog/getting-started-with-mcp1/connect.jpg)

The Connect page with General and Claude Code picked. Your page shows your own workspace in the command.

For Claude Code, copy the command and run it in your terminal:

Terminal

```
claude mcp add --transport http <workspace> https://mcp1.com/mcp/<workspace>/general
```

Then start Claude Code, run `/mcp`, pick your workspace’s server and choose **Authenticate**. Your browser opens MCP1\. Sign in, check the workspace, and approve the client.

Other clients work in a similar way:

Cursor

Select **Add to Cursor** on the Connect page. Cursor opens and asks to install the server. Authenticate when it asks.

VS Code

Select **Install in VS Code**. You need VS Code 1.101 or later.

Claude

Copy the URL. In Claude on the web or desktop, open **Settings → Connectors → Add custom connector**, paste the URL and approve MCP1.

ChatGPT

Copy the URL. In ChatGPT on the web, open **Plugins**, select the plus button, choose **Add custom MCP server**, paste the URL and choose OAuth.

Anything else

Pick Any MCP client and copy the URL. A client that speaks remote MCP finds out how to sign in by itself.

You only sign in once. Client tokens last eight hours and refresh on their own. To connect another client later, go back to the Connect page and use the same gateway.

## 5\. Make your first tool call

Ask your agent a question that needs the server. For DeepWiki, ask it about a public GitHub repository:

Prompt

```
Use DeepWiki to explain how routing works in the tanstack/router repository.
```

The agent calls `deepwiki__ask_question` through your gateway. MCP1 names every tool `server__tool`, so two servers with the same tool names never collide. Your client may ask you to allow the call the first time.

Claude · connected to MCP1 1 server

Use DeepWiki to explain how routing works in the tanstack/router repository.

1. `deepwiki__ask_question`Asked how routes are defined and matched in tanstack/routerDeepWiki

TanStack Router builds a typed route tree from your route files. Each file exports a route, and the generated tree gives every link and param its types…

1 call through mcp1.com/mcp/acme/general

A first call through the gateway, redrawn in MCP1’s colors.

Want to try a tool before you set up a client? Open **Playground**, pick a tool, fill in the form and select **Run**. It runs as you, under the same rules as your clients.

## Check that it worked

- **Get started** marks **Connect a client** and **Make your first call** as done.
- **Audit log** shows the call, with the tool, the client that made it and the result.
- **Clients** lists the app you approved. You can revoke it there at any time.

## If something doesn’t work

No tools show up

The gateway has no servers yet. Add one to General (step 3), then reconnect or refresh the server list in your client.

Can’t approve the client

Verify your email first. Open the link in the email MCP1 sent when you signed up.

A tool is missing

Ask your agent to call `mcp1__check_access`. It explains why a tool is or isn’t open to you.

The client has no sign-in

Create a key under **Keys** and send it as a bearer token. The Connect page shows the config under More ways and details.

## What’s next

Add the servers you use every day from [the catalog](https://mcp1.com/servers), like GitHub, Linear, Notion or Sentry. Put each one on General, and it shows up in every client you connected, without setting anything up again.

When you’re ready to bring your team in, read [10 steps for rolling out MCP across your company](https://mcp1.com/blog/rolling-out-mcp-to-your-company). [The docs](https://mcp1.com/docs) cover gateways, groups and policies in more detail.

## Common questions

### Is MCP1 free to start?

Yes. The Individual plan is free for one person and includes 15 servers and 3 gateways. Team and Enterprise add members, groups and higher limits.

### Do I need to set up each MCP server in every client?

No. Add servers to a gateway in MCP1 and connect each client to that gateway’s URL once. New servers on the gateway show up in every connected client.

### Can I use MCP1 with local MCP servers?

MCP1 connects to remote servers over HTTP or SSE, so a server has to be reachable at a public URL. Keep local-only servers, like ones that read your files, in your client.

### Where do I find my gateway URL?

Open Connect a client in your workspace and pick a gateway. Each gateway’s URL is https://mcp1.com/mcp/<workspace>/<gateway>, so the default one ends in /general.

Give your team one URL

Create a workspace, install your servers and share a gateway with a group. Free for individuals.

[Start with MCP1](https://mcp1.com/signup)[Read the docs](https://mcp1.com/docs)

## More from the blog

[ Terminal$ claude mcp add --transport http github api.githubcopilot.com/mcp/githubConnectedHow to connect GitHub MCP to Claude CodeRun claude mcp add with https://api.githubcopilot.com/mcp/ and a fine-grained token. Read-only mode, toolsets, permission rules and team setup.![](https://avatars.githubusercontent.com/u/1297371?s=96&v=4)Eldad FuxFounder and CEO, Appwrite](https://mcp1.com/blog/github-mcp-claude-code)[ SupportIntercomRead-onlyLinearRead-onlyNotionRead-onlyStripeRead-onlyMCP servers for support teams: what to connect firstStart with your helpdesk, Linear, Notion and Stripe, read-only first. What they answer together, which writes to hold back and a shared setup.![](https://avatars.githubusercontent.com/u/1297371?s=96&v=4)Eldad FuxFounder and CEO, Appwrite](https://mcp1.com/blog/mcp-servers-for-support-teams)

---

This is the markdown copy of https://mcp1.com/blog/getting-started-with-mcp1. Site index for agents: https://mcp1.com/llms.txt
