Direct answer: Add Finta as a remote MCP server in Codex with codex mcp add finta --url https://finta.ai/mcp. Complete the Finta authorization flow, confirm the intended organization, and begin with a read-only tool check.
Before you connect
- Install a current Codex CLI or use a Codex surface that shares its MCP configuration.
- Confirm that you can sign in to the intended Finta organization.
- Decide which relationship, CRM, document, or deal records belong in the first test.
- Never paste a Finta password, browser cookie, or access token into a prompt.
Add Finta to Codex
- Open a terminal in the project where you use Codex.
- Run
codex mcp add finta --url https://finta.ai/mcp. - Complete the browser authorization flow presented by Codex and Finta.
- Return to the terminal and run
codex mcp list. - Confirm that the server name is finta and the URL is exactly
https://finta.ai/mcp.
OpenAI's official Docs MCP guide documents the same codex mcp add <name> --url <server> flow for remote HTTP MCP servers.
Verify the connection without changing data
List the Finta tools available in this connection. Then search my Finta CRM for a contact I name. Do not create, update, send, schedule, enroll, archive, or delete anything.
Review the server name, selected Finta organization, tool name, and arguments before approving a request. A successful connection proves that Codex can reach the MCP server. It does not prove that the underlying CRM is complete or that a proposed action is correct.
Start with a useful workflow
- Build a second brain with Codex
- Audit CRM data with Codex
- Audit a fundraising data room with Codex
- Turn product milestones into investor evidence
- Build a fundraising reporting system
Permission checklist
- Start with search and read operations.
- Verify the intended Finta organization before every consequential tool call.
- Inspect sources before treating a generated conclusion as fact.
- Review CRM writes and every external communication separately.
- Remove the server from Codex if the device, workspace, or account changes hands.
Troubleshooting
| Problem | What to check |
|---|---|
| The server does not appear | Run codex mcp list and confirm the exact server name and URL. |
| Authorization does not finish | Sign in to Finta in the same browser, allow the callback to complete, then reconnect once. |
| No tools appear | Reconnect, confirm the selected organization, and refresh the Codex tool inventory. |
| The wrong records appear | Verify the Finta organization and inspect the record directly in Finta. |
| A tool request is blocked | Read the full permission, validation, credit, or confirmation message. Do not bypass it with repeated prompts. |
For broader diagnostics, use Troubleshoot a Finta MCP Connection, the Finta MCP tools reference, and Finta MCP security and permissions.
Limitations
- OpenAI controls Codex installation, MCP configuration, client-side approvals, and availability.
- Finta MCP only exposes tools permitted for the authorized Finta user and organization.
- Tool output can be incomplete when the underlying records or connected sources are incomplete.
- No MCP connection guarantees a meeting, introduction, investment, or fundraising outcome.
Verification status: The official Codex remote-MCP command pattern, the public Finta MCP endpoint, and linked Finta routes were reviewed 2026-09-28. After authorization, verify the server, organization, and tools presented to your account because client interfaces and permissions can change.