Skip to main content
The Meow MCP server speaks HTTP, the recommended transport for remote MCP servers. Pick your client below for copy-paste configuration. For how authentication and permissions work once you connect, see Authentication & scopes.

Choose a server URL

If you have a Meow account, use https://mcp.meow.com and sign in. Use https://mcp.meow.com/cli only when you don’t have an account yet and want agent-led signup. For the terminal, use the Meow CLI and run meow login.

Client setup

To open Cursor and add the Meow MCP automatically, click install. Or add the following to ~/.cursor/mcp.json. See the Cursor documentation.Install in Cursor
Don’t have a Meow account yet? Use the onboarding surface https://mcp.meow.com/cli for agent-led signup.

Client support matrix

The onboarding surface (mcp.meow.com/cli) serves agent-led signup only. Coding agents use mcp.meow.com with OAuth.

Agent-led signup

Don’t have a Meow account yet? Connect to https://mcp.meow.com/cli and ask your assistant to open one. The assistant walks you through the entire flow:
  • Call the start tool first. It returns step-by-step instructions, and each response tells the assistant what to do next.
  • Add, update, or remove owners and signers from the conversation.
  • Upload required documents through the assistant.
The assistant verifies your email with a six-digit code, then gets a 7-day onboarding key. The key works only with onboarding tools, and only while the business is onboarding or under review. After approval, sign in with OAuth at https://mcp.meow.com or run meow login to use your account. In the terminal, run meow onboarding start in the Meow CLI to start the same flow.
After each tool call, the assistant follows the step_instructions.directive field in the response. This keeps the guided signup on track without you leaving the chat.

Next steps

Authentication & scopes

Understand the OAuth flow and what each permission grants.

Tool reference

See every tool and example prompts to try.