Skip to main content
Vern runs a Model Context Protocol server, so an AI assistant you already use can work in your Vern account: look up companies, sources, templates and runs, update knowledge, create and run things, and start builds. These are the same operations the Home agent uses, with the same rules: an assistant can only do what the key allows, and deletes or sends to outside systems still need a person to confirm.

​
Endpoint

​
1. Create a key with MCP access

Go to Settings → API keys and click New key. Under MCP access, choose what the assistant may do: Start with Read and widen it later — you can edit a key’s access at any time. Keys created before MCP access existed are read-only until an Admin widens them.
Creating keys and changing their access is Admin-only. The assistant acts as the person who created the key, in that key’s company. MCP access doesn’t affect what the key can do on the Migration API.

​
2. Add Vern to your client

Run /mcp inside Claude Code to check it’s connected.
Treat the key like a password: keep it out of shared or committed config files where you can, for example by using your client’s environment-variable support.

​
3. Ask away

Try “What’s in my Vern account?” — the assistant starts with an overview, then digs in with the list and get tools. For example:
  • “Which runs failed this week, and why?”
  • “Read the knowledge on the Northwind source and tidy its structure.”
  • “Make external_id required on the Events template.”

​
What the tools cover

Which tools a client sees depends on the key’s access and on your plan — tools a key can’t use aren’t listed.

​
Confirmations

Deletes and anything that sends data outside Vern take two calls. The first returns approval_required with an action_id and a plain-English summary; the assistant should show you the summary and, only if you agree, call confirm_action with that id. Deletes also need the Delete access. Long builds (a migration, a writer or a source connector) run on their own after they start. If one needs an answer or credentials, finish it in Vern — credentials are never sent through MCP.

​
Limits and revoking

Requests are rate-limited per connection and per company. Delete a key on the API keys page and any client using it is cut off immediately.

​
Next

  • API keys — create, scope and revoke keys.
  • Home — the same agent, inside Vern.