How to integrate Dock certs MCP with Codex

Framework Integration Gradient
Dock certs Logo
Codex Logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Dock certs MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or app, whichever you prefer.

Composio removes the Authentication handling completely from you. We handle the entire integration lifecycle, and all you need to do is just copy the URL below, authenticate inside Codex, and start using it.

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 870+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Dock certs MCP in Codex

Codex CLI

Run the command in your terminal.

Terminal

This will auto-redirect you to the Rube authentication page.

Rube authentication redirect page

Once you're authenticated, you will be able to access the tools.

Verify the installation by running:

codex mcp list

If you otherwise prefer to use config.toml, add the following URL to it. You can get the bearer token from rube.app → Use Rube → MCP URL → Generate token

[projects."/home/user/composio"]
trust_level = "untrusted"

[mcp_servers.rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex in VS Code

If you have installed Codex in VS Code.

Then: ⚙️ → MCP Settings → + Add servers → Streamable HTTP:

Add the Rube MCP URL: https://rube.app/mcp and the bearer token.

VS Code MCP Settings

To verify, click on the Open config.toml

Open config toml in Codex

Make sure it's there:

[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
Codex App MCP Settings
  1. Restart and verify if it's there in .codex/config.toml
[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"
  1. Save, restart the extension, and start working.

What is the Dock certs MCP server, and what's possible with it?

The Dock certs MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Dock certs account. It provides structured and secure access to your verifiable credentials and decentralized identity management, so your agent can perform actions like issuing credentials, managing API keys, retrieving credential details, and automating webhook notifications on your behalf.

  • Instant credential issuance and management: Easily have your agent issue new verifiable credentials, retrieve detailed credential metadata, or delete outdated credentials as needed.
  • Secure API key lifecycle management: Direct your agent to create, list, retrieve, or delete API keys, ensuring secure programmatic access for your organization.
  • Automated webhook setup and oversight: Let your agent create or delete webhook endpoints, so you can receive real-time event notifications from Dock certs to your own systems.
  • Credential retrieval and decryption: Ask your agent to fetch specific credentials by ID, with options for full retrieval if protected by a password, ensuring secure and flexible access.
  • Tag and metadata cleanup: Enable your agent to delete obsolete tags or credential metadata, keeping your Dock certs environment organized and up to date.

Supported Tools & Triggers

Tools
Create API KeyTool to create an API key.
Create WebhookTool to create a webhook endpoint.
Delete API KeyTool to delete a specific API key.
Delete CredentialTool to delete a verifiable credential.
Delete TagTool to delete a specific tag.
Delete WebhookTool to delete a specific webhook.
Retrieve API KeyTool to retrieve details of an API key.
Retrieve API KeysTool to list all API keys.
Retrieve CredentialTool to retrieve a verifiable credential by its unique ID.
Retrieve CredentialsTool to retrieve a list of credential metadata.
Retrieve DID DocumentTool to retrieve a DID Document by its DID.
Retrieve Revocation RegistriesTool to retrieve a list of revocation registries.
Retrieve WebhookTool to retrieve a specific webhook's details.
Retrieve WebhooksTool to list configured webhooks.
Verify Credential or PresentationTool to verify a verifiable credential or presentation.

Conclusion

You've successfully integrated Dock certs with Codex using Composio's Rube MCP server. Now you can interact with Dock certs directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Dock certs operations
  • Managed authentication through Composio's Rube
  • Access to 20,000+ tools across 870+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Dock certs operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Dock certs MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Dock certs MCP?

With a standalone Dock certs MCP server, the agents and LLMs can only access a fixed set of Dock certs tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Dock certs and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Codex?

Yes, you can. Codex fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Dock certs tools.

Can I manage the permissions and scopes for Dock certs while using Tool Router?

Yes, absolutely. You can configure which Dock certs scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Dock certs data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.