Skip to main content
Connect your AI client to Firmngin to inspect devices, review entity history, operate permitted controls, and work with automations using natural language. Use this Firmngin MCP server URL in every supported client:

Codex and ChatGPT

Connect Codex clients or configure Firmngin as a custom app in ChatGPT web.

Claude

Connect Claude, Claude Desktop, or Claude Code to your workspace.

Cursor

Add Firmngin as a remote MCP server in Cursor.

OpenCode

Add and authenticate the Firmngin remote server from OpenCode.

​
Before you connect

You need:
  • A Firmngin account with access to at least one workspace.
  • An AI client that supports remote MCP servers and OAuth.
  • Permission to add custom connectors when your AI client is managed by an organization.
During connection, your browser opens Firmngin. Sign in, review the requested permissions, and approve only the access you expect the AI client to use.

​
Codex CLI and IDE

​
Codex CLI

Add Firmngin as a remote MCP server, authenticate it, then verify the connection:
The login command opens Firmngin in your browser for OAuth authorization. If your Codex version does not recognize login, update Codex before continuing.

​
Codex IDE

Open the MCP server settings from the gear menu, add a remote server, and use:
  • Name: firmngin
  • Transport: Streamable HTTP
  • URL: https://mcp.firmngin.dev
Save the server, authenticate when prompted, and confirm that Firmngin’s tools are available in the MCP panel.

​
ChatGPT web

ChatGPT web uses Apps rather than a generic desktop “MCP servers” screen. For an existing app, open Settings → Apps, select the app, choose Connect, and complete OAuth. To connect a private Firmngin MCP server as a custom app, your plan and workspace policy must support custom MCP apps. An admin or authorized developer may need to enable developer mode, add the Firmngin endpoint, scan its tools, configure allowed actions, and publish the app before other workspace members can use it. See Apps in ChatGPT and Developer mode and MCP apps in ChatGPT for the current availability and administrator steps.

​
Claude

​
Claude, Claude Desktop, and Cowork

1

Open Connectors

In Claude, open Customize, then select Connectors.
2

Add a custom connector

Select +, choose Add custom connector, and enter https://mcp.firmngin.dev as the remote MCP server URL.
3

Connect your account

Add the connector, select Connect, then sign in to Firmngin and approve the required permissions.
4

Enable it in a conversation

Use the + menu in a conversation, open Connectors, and enable Firmngin.
For Team and Enterprise organizations, an Owner or Primary Owner must add the custom connector before members can connect their accounts. See Claude custom connector setup.

​
Claude Code

Add Firmngin for your user account, then authenticate from an interactive Claude Code session:
Inside Claude Code, run:
Select Firmngin and complete the browser authorization flow. See the Claude Code MCP guide for scope and authentication options.

​
Cursor

Create or update ~/.cursor/mcp.json:
Restart Cursor after saving the file. Open Cursor’s MCP settings, locate Firmngin, and complete OAuth authentication when prompted. Cursor then makes the permitted Firmngin tools available to Agent.
Use .cursor/mcp.json in a project instead when the connection should only be available in that project.
See the Cursor MCP documentation for configuration locations and authentication behavior.

​
OpenCode

1

Add the server

Run opencode mcp add, choose a remote server, name it firmngin, and enter https://mcp.firmngin.dev.
2

Authenticate

Run opencode mcp auth firmngin. OpenCode opens the Firmngin authorization page in your browser.
3

Verify the connection

Run opencode mcp list and confirm that Firmngin is connected.
Add this entry to your OpenCode configuration when you prefer manual setup:
Then run opencode mcp auth firmngin.
See the OpenCode MCP documentation for remote server and OAuth options.

​
Other MCP clients

Firmngin can connect to another AI client when that client supports:
  • Remote MCP servers over Streamable HTTP.
  • OAuth authentication for the signed-in Firmngin user.
  • Tool discovery and tool calls.
Add https://mcp.firmngin.dev as the server URL, complete OAuth authorization, then confirm that the client can list Firmngin tools. Client-specific availability and administrator controls still apply.

​
What you can ask

After connecting, try prompts such as:
  • “List the devices in my default Firmngin workspace.”
  • “Show the current entities for the charging station device.”
  • “Summarize alarm events from the last 24 hours.”
  • “Show recent OTA activity for this device.”
  • “List my active automations and their latest executions.”
  • “Turn on this entity after I confirm the target device.”
The available result depends on the permissions you approved and the workspace selected for the request.

​
Permissions

Device control and management permissions can change your workspace or connected devices. Review every requested permission and tool confirmation before approving it.

​
Workspace selection

Firmngin uses your default workspace when workspace_id is not specified. To work with another workspace, ask the AI client to list your Firmngin workspaces first, then name or select the required workspace.

​
Disconnect access

Remove or disable Firmngin from the AI client’s MCP or connector settings to stop future tool calls. You can reconnect later and approve a new set of permissions.

​
Troubleshooting