Connect Finta MCP to Devin

Direct answer: In Devin, go to Settings, Connections, MCP servers, add Finta as a custom HTTP server with https://finta.ai/mcp, select OAuth, and choose the connection access deliberately. For individual relationship work, start with Personal access, complete Finta authorization, and use Test listing tools before running a read-only CRM request.

Before you connect

Check	Recommended state
Finta access	You can sign in and identify the Finta organization you intend to use.
Devin role	You have Manage MCP Servers permission.
Access model	Personal for individual relationship data, Organization only after an admin review.
Verification record	A non-critical CRM contact you are allowed to read.

Only Devin organization admins or users with the required MCP management permission can add a custom server. If Add a custom MCP is unavailable, ask your Devin administrator to review the connection instead of sharing credentials.

Cognition's current Devin MCP guide is the source of truth for custom server navigation, HTTP transport, OAuth, access sharing, and tool validation.

Add Finta as a custom HTTP server

Open Devin Settings.
Go to Connections, then MCP servers.
Select Add a custom MCP.
Enter Finta as the server name.
Add a short description such as Finta CRM and relationship tools.
Select HTTP as the transport.
Enter https://finta.ai/mcp as the server URL.
Select OAuth as the authentication method.
Choose Personal or Organization access using the guidance below.
Save the server.
Select Test listing tools.
Complete the Finta sign-in flow when Devin opens the authorization URL.
Select the intended Finta organization and return to Devin.

Use HTTP, which Devin documents as Streamable HTTP and recommends for new remote integrations. Do not use the legacy SSE option for this connection.

Finta publishes OAuth discovery and dynamic client registration metadata. You should not need to paste a Finta password, browser cookie, bearer token, client ID, or client secret into Devin.

Choose Personal or Organization access carefully

Devin's access setting determines who uses the authenticated connection.

Access	Who authenticates	Use for Finta when
Personal	Each Devin organization member connects an individual account	The relationship and CRM context belongs to that person's authorized Finta access.
Organization	Devin members share one authenticated connection	A Finta administrator has approved the shared identity, organization scope, and session-access model.

Personal access is the safer default for a founder's, GP's, or relationship owner's Finta account. Devin notes that other users may still interact with a person's Devin sessions, so Personal access should not be treated as a complete security boundary. Review session sharing separately.

Do not use Organization access with an employee's personal Finta identity merely for convenience. A shared connection can expose the same Finta authorization to every Devin member who can use it.

Verify the tool inventory

After the server is saved, select Test listing tools. Devin uses an isolated test environment to connect to the server and request its current tool list.

Then open a controlled Devin session and ask:

List the Finta tools available in this connection. Then search my CRM for a contact I name. Do not create, update, send, schedule, enroll, archive, or delete anything.

Review four separate proofs:

Connectivity: Devin reaches the Finta server.
Authentication: The connection completes Finta OAuth.
Tool discovery: Finta tools appear in the current inventory.
Organization scope: A read-only call returns a record from the intended Finta organization.

Test listing tools verifies discovery. It does not prove the correct organization, complete records, or safe use of every action.

Keep relationship data out of broad Devin sessions

Finta relationship intelligence can include CRM notes, deal context, network evidence, communication history, and timing. Before using that data in Devin:

Use Personal access unless a shared connection is explicitly approved.
Restrict the Devin session to the people who need the relationship context.
Keep the first test read-only.
Review the Finta tool name, arguments, organization, and target record before any write.
Do not place retrieved private context into public repositories, issue descriptions, build logs, or shared artifacts.
Disconnect the MCP server when the project or team access ends.

Devin controls the agent session and its sharing model. Finta separately enforces the authorized organization, user access, validation, and current server-side action boundaries.

How Finta helps in Devin

Devin can work across code, repositories, and connected tools. Finta adds current capital-workflow context: supported contacts, companies, deals, network evidence, documents, tasks, communication context, and pipeline state.

That can be useful when a team is building an internal fundraising workflow, debugging a CRM integration, or preparing a source-linked brief for a product decision. Finta remains the durable relationship record. A model-generated summary or possible network path does not establish consent, endorsement, investor interest, or permission to contact someone.

Troubleshooting

Add a custom MCP is missing

Confirm that you have Manage MCP Servers permission. Organization admins control custom server creation in Devin.

Test listing tools reports a network error

Confirm the transport is HTTP and the URL is exactly https://finta.ai/mcp. Finta must be reachable from Devin's network.

Devin reports an authentication error

Confirm OAuth is selected, complete the browser flow, and return to Devin. Finta publishes dynamic registration metadata, so adding manual client credentials should not be the first fix.

The server connects but no tools appear

Run Test listing tools again, inspect Devin's reported error, and confirm that authentication completed before retrying a session.

Another Devin user can access the same Finta connection

Check the server's Access setting. Organization access shares one connection. Reconfigure it as Personal unless shared access was deliberately approved.

The result comes from the wrong Finta organization

Disconnect the Finta authorization, authenticate again, and select the correct organization. Do not attempt to change organization scope through a prompt.

Limitations

Cognition controls Devin plans, permissions, custom MCP management, session sharing, OAuth handling, tool validation, and model behavior.
Personal MCP access is not a complete security boundary because other users may be able to interact with a shared Devin session.
Organization access can expose one authenticated Finta connection to multiple Devin users.
Tool results depend on the selected Finta organization, user permissions, connected sources, data quality, product configuration, and current tool inventory.
Finta MCP does not guarantee complete records, correct model reasoning, introductions, replies, commitments, or fundraising outcomes.

Related guides

Verification status: August 21, 2026. The public Finta endpoint, Finta OAuth discovery metadata, and current Devin MCP documentation were verified. An authenticated Devin tool receipt remains a publication proof requirement.

Explore Aurora and connect Finta