How to integrate Bidsketch MCP with Codex

Framework Integration Gradient
Bidsketch Logo
Codex Logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Bidsketch 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 Bidsketch 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 Bidsketch MCP server, and what's possible with it?

The Bidsketch MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Bidsketch account. It provides structured and secure access to your proposals and client data, so your agent can perform actions like creating clients, managing proposals, organizing sections, and handling fees on your behalf.

  • Client creation and management: Easily have your agent add new clients to Bidsketch or retrieve detailed client information by ID.
  • Proposal organization and cleanup: Direct your agent to list, delete, or manage proposals for specific clients, streamlining your workflow and keeping things tidy.
  • Section and fee management: Let your agent add or remove proposal sections and fees, ensuring each proposal is perfectly structured before sending.
  • Webhook and automation controls: Remove webhooks or automate repetitive admin tasks to keep your Bidsketch account running smoothly with minimal manual effort.

Supported Tools & Triggers

Tools
Create ClientTool to create a client.
Delete ClientTool to delete a client and all their proposals.
Delete FeeTool to delete a fee.
Delete ProposalTool to delete a proposal and all its content.
Delete Proposal FeeTool to delete a proposal fee.
Delete Proposal SectionTool to delete a proposal section.
Delete SectionTool to delete a section.
Delete WebhookTool to delete a webhook.
Get ClientTool to get a client by id.
Get Client ProposalsTool to list proposals for a specific client.
Get ClientsTool to retrieve all clients.
Get FeeTool to get a single fee.
Get FeesTool to list all the fees for the account.
Get ProposalTool to get a proposal by id.
Get Proposal ContentTool to get a proposal with all its content (sections and fees).
Get Proposal FeeTool to get a single fee item for a proposal.
Get Proposal FeesTool to list all fees for a proposal.
Get ProposalsTool to retrieve all proposals for the account.
Get Proposal SectionTool to fetch a single proposal section.
Get Proposal SectionsTool to get all sections for a proposal.
Get Proposal StatsTool to get proposal statistics.
Get SectionTool to fetch a section by id.
Get SectionsTool to list all sections.
Get TemplatesTool to list all proposal templates saved for the account.
Create FeeTool to create a fee.
Create Proposal FeeTool to create a proposal fee.
Create Proposal SectionTool to create a proposal section.
Create SectionTool to create a section.
Create WebhookTool to create a webhook.
Update ClientTool to update a client.
Update FeeTool to update a fee.
Update ProposalTool to update a specific proposal's details.
Update Proposal FeeTool to update a proposal fee.
Update Proposal SectionTool to update a proposal section.
Update SectionTool to update a section.

Conclusion

You've successfully integrated Bidsketch with Codex using Composio's Rube MCP server. Now you can interact with Bidsketch 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 Bidsketch 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 Bidsketch operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Bidsketch MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Bidsketch MCP?

With a standalone Bidsketch MCP server, the agents and LLMs can only access a fixed set of Bidsketch tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Bidsketch 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 Bidsketch tools.

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

Yes, absolutely. You can configure which Bidsketch 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 Bidsketch 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.