Does Pledge work with Codex?

Yes. Add Pledge as an MCP server in Codex, sign in once, and the agent can draft, edit and send contracts from your templates.

Does Pledge work with Cursor?

Yes. Install the Pledge plugin from Cursor's marketplace or add the MCP server under Settings, then sign in.

Can the agent read my project files to write the scope?

Your coding agent can read files in your project as usual, and use them to fill in the statement of work it drafts in Pledge. Pledge only receives the contract, not your code.

Send a statement of work from Codex or Cursor without leaving your editor

Published 30 October 2026

Short answer

If you run a dev shop or technical consultancy, your day is spent in Codex or Cursor. Connect Pledge as an MCP server and you can ask the same agent to draft a statement of work from your template, check it, and send it for signature, without switching to another app.

Why contracts belong next to the code

Technical consultancies sell work that's described in technical terms: endpoints, integrations, milestones, environments. The person who knows the scope best is often the one with the editor open. Moving that knowledge into a separate contract tool means copying, retyping and context switching.

With an MCP connection, the agent in your editor can do it for you:

Draft a statement of work for Acme from our SOW template: the payments integration we scoped in docs/acme.md, three milestones, 18 000 fixed. Send it to their CTO.

Connect Pledge to Codex

In Codex, open Plugins, then Add, then Add custom MCP server, and paste the server address from Pledge's agent guide. Or in the terminal:

codex mcp add pledge --url (the server address)

Codex opens Pledge's connect page in your browser. Sign in, pick the workspace and the access level, and press Allow.

Connect Pledge to Cursor

Add the Pledge plugin from Cursor's marketplace, or add the server under Settings, then MCP, and sign in. The same connect page appears.

What the workflow looks like

Ask for the draft. Point the agent at the notes or tickets that describe the work.
Review it. In Cursor the contract can appear as an editable document in the chat. In Codex the agent shows it as text, with a link to the draft in Pledge.
Adjust. "Move milestone two to January", "add a clause on hosting costs".
Send. Tell the agent to send it. It never sends on its own.
Track it. "Has Acme signed?" works from the same chat.

Bring the scope and the terms together

From the project
Notes and tickets
The work, deliverables and milestones you already scoped.
From Pledge
Your SOW template
The structure and terms for the new agreement.

Combined into

A draft statement of work

Client, scope, price and milestones ready for you to check.

Review and adjust the draft before asking the agent to send it.

Project notes supply the scope; your template supplies the agreement’s structure. The agent combines them into a draft for review.

A good SOW prompt has four parts

The client and who signs
The template to start from, if you have more than one
The scope, ideally pointing at a file the agent can read
The commercial terms: price, milestones, payment terms

See the statement of work template and prompt for a full example.

Questions

Does Pledge work with Codex?: Yes. Add Pledge as an MCP server in Codex, sign in once, and the agent can draft, edit and send contracts from your templates.
Does Pledge work with Cursor?: Yes. Install the Pledge plugin from Cursor's marketplace or add the MCP server under Settings, then sign in.
Can the agent read my project files to write the scope?: Your coding agent can read files in your project as usual, and use them to fill in the statement of work it drafts in Pledge. Pledge only receives the contract, not your code.

Try Pledge

Contracts, time, plans and leads for small agencies, with an MCP server for Claude and ChatGPT. Pledge is in private beta: leave your email and we will send an invite.