Skip to content

Agent Toolkit

The iMBrace Agent Toolkit is the official iMBrace plugin for AI coding agents. Install it once, and your agent knows how to build on iMBrace: the TypeScript/Python SDK, the hosted MCP server, the CLI, AI agents, workflows, knowledge hubs and CRM boards.

The plugin is called iMBrace Developer. It ships in two forms:

  • Claude Code — the six skills plus the hosted iMBrace MCP server, so the agent can also read (and, if you allow it, change) your iMBrace data.
  • ChatGPT and Codex — the same six skills, as a skills-only plugin. It contains instructions only; it does not call any service and holds no credentials. Connect the MCP server yourself if you want tools (Other MCP clients).

Source and issues: github.com/imbrace-co/imbrace-agent-toolkit (MIT).

What’s in the toolkit

SkillUse it for
imbrace-get-startedFirst use: pick an environment, get an API key safely, make one verified call
imbrace-sdkTypeScript @imbrace/sdk and Python imbrace: client setup, namespaces, errors
imbrace-mcpConnect the hosted MCP server in any client; OAuth sign-in, API key fallback
imbrace-cliInstall, sign in and script the imbrace CLI; run imbrace mcp locally
imbrace-build-agents-workflowsAI agent + streaming chat, workflows, knowledge hubs, CRM boards end to end
imbrace-vibe-codeBuild, deploy and host a full app on iMBrace (follows /skill.md)

Skills load on their own when your request matches. Start a new session and ask, for example, “Help me get started with iMBrace”.

Install in Claude Code

Requires Claude Code 2.1.275 or later. From a terminal:

Terminal window
claude plugin marketplace add imbrace-co/imbrace-agent-toolkit
claude plugin install imbrace-developer@imbrace-developer-tools

Or inside a Claude Code session:

/plugin marketplace add imbrace-co/imbrace-agent-toolkit
/plugin install imbrace-developer@imbrace-developer-tools

Update with claude plugin marketplace update imbrace-developer-tools; remove with claude plugin uninstall imbrace-developer.

Choose the environment

The plugin adds the MCP server as imbrace, with no credential stored in the plugin. It connects to production; the MCP URLs of every environment are:

EnvironmentMCP URL
Production (the plugin’s server)https://app-gatewayv2.imbrace.co/mcp
Sandboxhttps://app-gateway.sandbox.imbrace.co/mcp
On-premisehttps://<your gateway>/mcp

For another environment, add a server of your own (below). Each environment has its own accounts, organizations and API keys: sign in, or generate the key, in the environment you connect to. Adding ?services= or ?tags= to the URL narrows the tools that are listed and can be called (see MCP Server); that is a filter, not access control.

Use several environments

The plugin’s imbrace server always points to production. Add each other environment under its own name; each one signs in separately (disable the plugin’s server with /mcp if you only want the other environment):

Terminal window
claude mcp add --transport http imbrace-sandbox https://app-gateway.sandbox.imbrace.co/mcp
claude mcp add --transport http imbrace-onprem https://<your gateway>/mcp

Then /mcp → each server → Authenticate. On a gateway without OAuth, add --header "Authorization: Bearer $IMBRACE_SANDBOX_API_KEY" to the command instead, with one key variable per environment. Tools are listed per server (for example mcp__imbrace-sandbox__listBoards), so say which environment you mean when you ask.

ChatGPT and Codex

The same skills will be published in the OpenAI plugin directory as iMBrace Developer; the listing link is added to the toolkit README on release. This package is skills-only: to give Codex the iMBrace tools as well, add the MCP server to Codex as shown under Other MCP clients.

Connect the MCP server

There are two ways to sign in, one per connection: OAuth (sign in in the browser, nothing to copy) and an API key (api_...).

Sign in with OAuth

Where the gateway has OAuth enabled:

  1. In Claude Code, run /mcp, select imbrace and choose Authenticate.
  2. Sign in to iMBrace in the browser that opens.
  3. On the consent screen, pick the organization this connection works in.
  4. Choose the access to grant: read only, or read + write (and delete, if you need it). You can untick write and delete.
  5. Back in Claude Code the tools appear. Try “List my iMBrace boards” — it should call a tool such as listBoards.

What you grant

ScopeAllows
imbrace.readRead tools. Always granted.
imbrace.writeCreate and update tools
imbrace.deleteDelete tools (implies write)
  • The organization is fixed by the grant. Every call runs in the organization you picked on the consent screen; an organization the client or the model sends is overwritten. To work in another organization, sign in again.
  • Write and delete come only from these scopes. With OAuth, ?allowWrite and ?allowDestructive on the URL are ignored.
  • Every tool call is replayed through the normal API as you, so your membership, role permissions and licences in that organization still apply.

Sessions, switching and revoking

  • The client stores and refreshes the token itself. An access token lasts 1 hour and is renewed with a refresh token, so you don’t sign in every hour.
  • Switch organization or access: /mcp → imbrace → clear authentication, then Authenticate again and make a new choice.
  • Revoke: clear authentication in the client to delete the tokens it stored. Access tokens are not checked against a revocation list, so one that was already issued stays valid until it expires (at most 1 hour). Removing a person from the organization or changing their role takes effect immediately, because the gateway checks membership and role on every call.

API key instead

Use an API key where the gateway does not have OAuth enabled yet, for CI and headless machines, and for clients without OAuth. Generate an org key (api_...) in the iMBrace Portal under GovernCore → Generate External Token (see Getting an API Key), and put it in an environment variable yourself — never paste the key into the chat or commit it.

In Claude Code, add the server with the key, and disable the plugin’s imbrace server (or the plugin) if you don’t want two entries:

Terminal window
claude mcp add --transport http imbrace https://app-gatewayv2.imbrace.co/mcp \
--header "Authorization: Bearer $IMBRACE_API_KEY"

An API-key connection is read-only unless the URL has ?allowWrite=1 (create and update) or ?allowDestructive=1 (also delete). A static Authorization header turns off the client’s OAuth flow, so use one method per connection.

Other MCP clients

The examples use production; replace the host with your environment’s gateway. The OAuth variants apply only where the gateway has OAuth enabled.

OAuth:

Terminal window
claude mcp add --transport http imbrace https://app-gatewayv2.imbrace.co/mcp

Then /mcp → imbrace → Authenticate. With an API key, use the command in API key instead.

Claude on the web, desktop and mobile (custom connector)

Without Claude Code, connect iMBrace to Claude — claude.ai, Claude Desktop and the mobile apps — as a custom connector. This needs a gateway with OAuth enabled: a custom connector cannot send an API key.

  1. Open Settings → Connectors and choose Add custom connector. On a Team or Enterprise plan, an Owner adds it first in the organization’s connector settings; members then connect it from their own settings.
  2. Name it after the environment, for example iMBrace or iMBrace (sandbox), and paste the MCP URL from Choose the environment. Leave the advanced OAuth client ID and secret empty: Claude registers itself with iMBrace.
  3. Choose Connect, sign in to iMBrace, and on the consent screen pick the organization and the access (read, write, delete).
  4. In a chat, turn the connector on from the tools menu, then ask, for example, “List my iMBrace boards”.
  • One connector per environment and organization. To switch organization or access, disconnect the connector and connect it again.
  • The gateway must be reachable from the internet. Claude connects from Anthropic’s cloud, not from your computer. An on-premise gateway behind a VPN or firewall works only from Claude Code, or from another client running on a machine that can reach it.
  • A connector added on claude.ai is also available in Claude Desktop and the mobile apps.

Troubleshooting

SymptomCauseFix
/mcp shows imbrace as failed: Dynamic Client Registration rejected (HTTP 404) … Cannot POST /registerOAuth is not enabled on that gateway, so sign-in cannot startDisable the plugin’s imbrace server and connect with an API key
401 with invalid_tokenNot signed in, or the sign-in expired/mcp → imbrace → clear authentication, then Authenticate again
401 with an API keyThe key is wrong, expired, from another environment, or emptyCheck the key and the gateway host
403Your role in that organization lacks the permissionAsk an organization admin
402 plan_feature_unavailable (MCP access is not included in your plan)The organization’s plan does not include MCP accessAsk an iMBrace admin to enable MCP access for the plan, or re-authenticate and pick an organization whose plan includes it
Write or delete tools missing, or tool not enabledOAuth: the grant lacks imbrace.write / imbrace.delete. API key: the URL lacks ?allowWrite=1 / ?allowDestructive=1. Or a ?services= / ?tags= filter excludes the toolRe-authenticate and grant write (or delete), or fix the URL
A custom connector cannot connectThe gateway has no OAuth, or is not reachable from the internetCheck <gateway>/.well-known/oauth-protected-resource/mcp. Use a gateway with OAuth, or Claude Code with an API key

Support

Report problems and ask questions in the toolkit’s GitHub Issues.

The MCP server is operated by iMBrace Limited. Calls run as the iMBrace user and organization you sign in with (or with your API key), under the iMBrace privacy policy and terms. The skills only suggest commands and code; when you run them, they call iMBrace services (and npm or PyPI to install the SDK and CLI), listed under Network and data in the plugin README.