MyApi

ONE CONNECTION. YOUR CHOICE OF AGENT.

Your next agent.
Already connected.

Give Claude Code or Cursor access to the tools you already use. Connect your accounts once in MyApi, choose what each agent can do, and keep your provider credentials in the vault.

Set up my agent See the product demo

An existing AI client + a MyApi account. Start with one service.

FROM SETUP TO FIRST REQUEST

Make one useful connection.

Use the Quick Connect flow below for a client that can run a local MCP server.

02

Choose its access

In Access Tokens, create a scoped token for that service. Start with read access. In Connectors → Quick Connect, choose that scope template and generate a setup prompt.

Quick Connect also offers full account access. Check your selection before generating the code.

03

Add MyApi to your agent

Choose your client for the setup details. Use the fresh code from your dashboard in place of YOUR_ENROLL_CODE. It is single-use and expires after 15 minutes.

The code grants the selected access until consumed or expired. Keep it private. After enrollment, a local Ed25519 key signs requests.

Connect Claude Code

Run this in your terminal after replacing YOUR_ENROLL_CODE. This adds MyApi for your user account.

Terminal
claude mcp add --scope user --transport stdio --env MYAPI_ENROLL_CODE=YOUR_ENROLL_CODE myapi -- npx -y myapi-asc-mcp

Open Claude Code and check /mcp. Allow MyApi if prompted, then ask it to call myapi_status.

Official Claude Code MCP instructions

Requires Node.js 18 or later and npm on the machine running your client. Merge the MyApi entry into an existing configuration; keep your other servers.

04 · VERIFY, THEN ASK

Make the first call count.

Restart or reload your MCP server, then paste this into your agent. A configured server alone does not prove that access works.

Call myapi_status to verify MyApi. Tell me the access level you received, then list the connected services available to you. Do not read messages, change data, or send anything.

Success: the status tool confirms signed access and your agent lists the services within its permissions. You can then ask it to read a specific service.

If something gets in the way.

The code expired or was already used

Generate a fresh setup prompt in Quick Connect and replace the code in your MCP configuration. Restart the server and call myapi_status again. On a successfully enrolled machine, the same consumed code can remain in the configuration; subsequent sessions use the saved key.

My agent cannot run npx or change its MCP configuration

This guide is for clients that can launch local processes. A browser chat or managed runtime may not allow that. Open Connectors for the hosted OAuth or assistant-specific options available for your client. Do not paste this command into a chat and assume a server was installed.

The connection works, but a service is missing or denied

Check that the service is connected in MyApi and included in your agent’s scope. A 403 may mean the scope does not allow the request. Adjust the access you intend to grant, generate a new code, and re-enroll. For an unexpected failure, ask the agent to call myapi_diagnose.

What else travels with my agents?

MyApi also supports reusable personas, skills, knowledge documents, and memory. Add them once your first service works. The gateway also provides service proxies, device controls, usage limits, audit history, and workspaces. See the product documentation for the full model.

Can I undo the connection?

You can pause or revoke agent access from Devices. The provider connection remains separate. Review the security documentation for the access model and current limitations.

LESS SETUP. MORE USEFUL WORK.

Start with the agent you already use.

Connect one service. Try one task. Add more when you need it.

Get started with MyApi