Installation

Add the trame MCP server to your CLI.

Prerequisites
You need an MCP-compatible CLI tool installed (any tool that supports the Model Context Protocol).
1

Add trame to your MCP config

Add trame as an MCP server in your client's configuration. The exact config file varies by client, but the MCP server definition is the same:

1{
2  "mcpServers": {
3    "trame": {
4      "url": "https://trame.sh/mcp",
5      "transport": "http"
6    }
7  }
8}
For local development, use http://localhost:3001/mcp instead. Consult your MCP client's documentation for the exact config file location and format.
2

Restart your MCP client

Restart or reload your CLI tool to pick up the new MCP server. Check the MCP status to confirm trame appears in the server list.

3

Authenticate

On first use, your MCP client triggers the OAuth flow:

  1. Browser opens the trame login page
  2. Sign in with Google or email
  3. Grant access to trame
  4. Token is stored and refreshed automatically
4

Verify

Test your setup:

1Show me all my trame projects

An empty list means everything is working. You're ready to create your first project.

Troubleshooting

MCP server not connecting

  • Check the trame URL in your MCP client config
  • Ensure the server is enabled in your config
  • Restart your MCP client completely (not just reload)

Authentication fails

  • Check that popups are not blocked
  • Clear browser cache/cookies for trame.sh
  • Complete all steps of the OAuth flow

Local development

  • Start the MCP server: just dev
  • Verify PostgreSQL is running with migrations applied
  • Start the Firebase emulator: just start-emulator
  • Use http://localhost:3001/mcp in config