Direct answer: To use Finta MCP with GitHub Copilot in Visual Studio Code, add https://finta.ai/mcp as a remote HTTP server, complete Finta OAuth, and use the Local chat harness with the Agent role. As of August 21, 2026, the separate Copilot Agent Host harness cannot use authenticated remote MCP servers, so it is not the right target for Finta.
Check the current scope first
Visual Studio Code now separates the chat model from the agent harness that runs tools. That distinction matters for an authenticated Finta connection.
| VS Code surface | Finta MCP status | Why |
|---|---|---|
| Main Chat view, Local harness, Agent role | Configuration path documented below | The Local harness can use configured MCP servers. |
| Copilot Agent Host harness | Not supported for this setup | Current VS Code documentation says the Copilot harness can access only local MCP servers that do not require authentication. |
| Copilot cloud agent on GitHub.com | Not covered by this guide | Cloud sessions use the tools and MCP servers configured by the cloud service. |
| GitHub Copilot CLI | Not covered by this guide | The CLI has its own MCP configuration and OAuth behavior. |
This page is intentionally scoped to GitHub Copilot Chat in the main Visual Studio Code window. It does not claim that every Copilot surface can connect to Finta.
See the current VS Code agent harness guide for the authenticated remote-server limitation and GitHub's Copilot Chat MCP guide for the IDE workflow and managed-plan policy.
Before you connect
| Check | Recommended state |
|---|---|
| Finta access | You can sign in and identify the Finta organization you intend to use. |
| VS Code | Updated to a current release with MCP support. |
| GitHub Copilot | Signed in and available in VS Code. |
| Organization policy | MCP servers in Copilot is enabled when your Business or Enterprise administrator controls it. |
| Approval mode | Manual approval remains enabled while you inspect the tools. |
Add Finta as a remote MCP server
- Open the Visual Studio Code Command Palette.
- Run MCP: Add Server.
- Choose HTTP as the server type.
- Enter
https://finta.ai/mcpas the URL. - Name the server Finta.
- Save it to your user profile for an individual test, or to the workspace only if the team has reviewed the shared configuration.
- Start the server and review the trust prompt.
- Complete the Finta sign-in flow in the browser.
- Select the intended Finta organization and return to VS Code.
You can also add the server manually. Run MCP: Open User Configuration for a user-level connection, or edit .vscode/mcp.json for a repository-level configuration.
{
"servers": {
"finta": {
"type": "http",
"url": "https://finta.ai/mcp"
}
}
}
Do not add a Finta password, OAuth token, browser cookie, or private header to this file. Finta publishes OAuth discovery metadata, and VS Code can handle the browser authorization flow.
Use Microsoft's VS Code MCP server guide and MCP configuration reference as the source of truth for current file locations and fields.
Use the correct chat harness
- Open the main VS Code Chat view.
- Start a new chat.
- Choose Local in the Session Target control.
- Choose the Agent role.
- Open Configure Tools and confirm that Finta tools are visible.
- Enable only the read tools needed for the first test.
If your VS Code release does not show a Session Target control, use the standard Copilot Chat panel in Agent mode and confirm that the configured server appears under MCP: List Servers. Current navigation can change, so the official VS Code MCP guide remains the source of truth.
Verify without changing CRM data
Start with this prompt:
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.
Check three things before expanding access:
- Tool discovery: Finta appears in the tool picker and the tool names are readable.
- Organization scope: The result comes from the intended Finta organization.
- Read-only outcome: The response retrieves a record without proposing or executing a change.
A green server indicator proves connectivity, not the completeness or accuracy of the CRM record.
Keep relationship context controlled
Finta can make supported CRM, deal, network, inbox, calendar, document, and workflow context available through its current tool inventory. That context can include sensitive relationship history and timing. Use the narrowest practical setup:
- Prefer a user-level server while testing.
- Keep approvals on for every tool call during setup.
- Enable only the Finta tools needed for the current task.
- Do not copy private relationship context into repository files or reusable public prompts.
- Review the target organization and record before approving a write.
- Revoke the connection when a device, workspace, or team role changes.
Finta remains the organization-scoped system of record. VS Code supplies an agent interface, but it does not broaden the Finta user's permissions.
How Finta helps inside a development workflow
A founder, investor, or operations team may build scripts, dashboards, or internal tools while also needing current fundraising context. Finta MCP gives a supported client a governed path to that context without turning a spreadsheet export into a second CRM.
For example, a user can inspect a contact or deal before changing an internal workflow, prepare a relationship brief from authorized records, or check whether a proposed automation matches the current pipeline. Relationship evidence is still evidence to review. It does not establish consent, investor interest, or permission to contact someone.
Troubleshooting
Finta does not appear under MCP servers
Run MCP: List Servers, confirm the URL is exactly https://finta.ai/mcp, and restart the server after editing the configuration. Avoid defining the same server in both user and workspace configuration.
The browser sign-in does not open
Start or authenticate the server from the CodeLens above its configuration, or select the server from MCP: List Servers and choose the authentication action. Confirm pop-ups and callback URLs are not blocked.
Authentication succeeds but the agent cannot use Finta
Confirm the chat uses the Local harness. The current Copilot Agent Host harness does not support authenticated remote MCP servers.
The server connects but no tools appear
Restart the server to refresh tool discovery, inspect the MCP output log, and confirm that the Finta tools are enabled in Configure Tools.
The result comes from the wrong organization
Disconnect Finta, reconnect, and select the correct organization during authorization. Do not attempt to work around organization scoping with prompts.
Limitations
- GitHub and Microsoft control VS Code, Copilot plan access, organization policy, chat harnesses, and tool approval behavior.
- This guide does not cover GitHub Copilot CLI, the Copilot cloud agent, GitHub.com code review, or the current Copilot Agent Host harness.
- 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.
- Review material information and every consequential action with the appropriate person.
Related guides
- Introducing Finta's Aurora MCP
- Finta MCP tools reference
- Finta MCP security and permissions
- Troubleshoot Finta MCP
- Use Finta MCP for relationship intelligence
Verification status: August 21, 2026. The public Finta endpoint and OAuth discovery metadata were verified in production. An authenticated GitHub Copilot in VS Code tool receipt remains a publication proof requirement.