Skip to main content
Firmhouse MCP lets an AI agent connect to Firmhouse through the Model Context Protocol. Use it when you want an agent in Claude, ChatGPT, Codex, or another MCP-capable workspace to help with Firmhouse project context. MCP support differs per agent product, but most remote MCP setup flows ask for the same information: a server URL, a connection type, and an authentication step.

​
MCP server URL

Use the Firmhouse MCP server URL: 
https://mcp.firmhouse.com/mcp
When your agent asks for the connection type, choose the remote HTTP or Streamable HTTP option. Some products call this streamable-http, Streamable HTTP, or simply a remote MCP server.

​
Basic setup flow

In your agent or AI workspace:
  1. Open the settings for tools, connectors, integrations, or MCP servers.
  2. Add a new MCP server or connector.
  3. Name the connection Firmhouse.
  4. Set the server URL to https://mcp.firmhouse.com/mcp.
  5. Choose the Streamable HTTP or remote MCP server type if the agent asks for one.
  6. Use the authentication function available in the agent.
  7. Sign in to Firmhouse when prompted.
  8. Select the Firmhouse project and permission scope the agent may access.
  9. Approve the connection.
After approval, return to your agent and confirm that Firmhouse tools are available. Start with a simple question to verify that the connection can read the selected project: 
Can you give me the name of my project?

​
Example configuration

Some agents let you configure remote MCP servers with JSON. The exact field names depend on the product, but the configuration usually looks similar to this: 
{
  "mcpServers": {
    "firmhouse": {
      "type": "streamable-http",
      "url": "https://mcp.firmhouse.com/mcp"
    }
  }
}
Other agents use a visual setup flow instead of JSON. In that case, use the same values in the form: name the connection Firmhouse, use the Firmhouse MCP URL, select Streamable HTTP or remote MCP, and complete authentication through the agent.

​
Authentication and permission scopes

Firmhouse MCP uses the authentication flow provided by your agent. The agent redirects you to Firmhouse, where you sign in and approve what the connection may access. During authorization, select:
  • the Firmhouse project this agent connection may use
  • the permission scope you want to grant
  • the Firmhouse user account that should own the connection
Only grant the scope the agent needs for the work you plan to do. If you are unsure which scope to choose, start with the most limited option available or contact Firmhouse support.

​
One user, one project

Each Firmhouse MCP connection is scoped to a single Firmhouse user in a single Firmhouse project. This means:
  • the agent can only use Firmhouse data and tools for the project selected during authentication
  • the connection acts on behalf of the Firmhouse user who approved it
  • project access follows what that user is allowed to access in Firmhouse
If you want your agent to work with multiple Firmhouse projects, add multiple Firmhouse MCP connections. Create one connection per project, and give each connection a clear name such as Firmhouse - Netherlands or Firmhouse - B2B project.

​
Troubleshooting

​
The agent cannot connect

Check that the server URL is exactly: 
https://mcp.firmhouse.com/mcp
Also confirm that the agent supports remote MCP servers. Some tools only support local command-based MCP servers.

​
Authentication does not start

Use the authentication or authorization function built into your agent’s MCP setup flow. Do not add a static bearer token unless Firmhouse support explicitly asks you to.

​
You do not see the expected project

Firmhouse only shows projects available to the signed-in user. Confirm that you are signed in with the right Firmhouse account and that agent capabilities are enabled for that project.

​
You need access to another project

Add a second Firmhouse MCP connection and select the other project during authentication. Each connection is project-specific.