Direct answer: Add Finta to OpenClaw as a remote Streamable HTTP MCP server, use https://finta.ai/mcp as the URL, select OAuth, and run a live probe before giving an agent access to Finta tools. OpenClaw's current documentation supports this configuration, but the exact OAuth experience depends on the installed OpenClaw version.
Check your OpenClaw version first
OpenClaw is changing quickly. When this guide was researched on August 21, 2026, its GitHub releases page listed 2026.7.1-2 as the latest stable release. An official OpenClaw issue reproduced a missing OAuth loopback listener in that release. The issue is closed and the current main-branch documentation describes an automatic callback, but you should not assume your installed build includes that fix.
| Check | Recommended state |
|---|---|
| Finta access | You can sign in and select the intended Finta organization. |
| OpenClaw version | You have updated to a release that includes the remote MCP OAuth callback fix, or you are prepared to complete the documented manual code fallback. |
| Transport | Streamable HTTP, not the legacy SSE default. |
| Initial scope | Test in a personal or controlled environment before publishing the connector to a shared Gateway. |
OpenClaw's MCP CLI documentation is the source of truth for the commands below.
Add the Finta server from the CLI
Run:
openclaw mcp add finta \
--url https://finta.ai/mcp \
--transport streamable-http \
--auth oauth
This saves a server named finta. Saving a definition is not proof that the remote server is reachable or authorized.
Inspect the saved configuration:
openclaw mcp show finta --json
openclaw mcp status --verbose
Confirm that the URL is exactly https://finta.ai/mcp, the transport is streamable-http, and authentication is oauth. Do not add a Finta password or long-lived bearer token to the command, a repository, or an agent prompt.
Complete Finta OAuth
Start the authorization flow:
openclaw mcp login finta
Open the authorization URL, sign in to Finta, select the organization you intend to use, and review the requested access.
On a release with the current callback implementation, OpenClaw should receive the callback and finish the token exchange. If the browser returns to a loopback URL that does not load, do not paste the entire callback URL into chat. Copy only the code query parameter and use OpenClaw's documented fallback:
openclaw mcp login finta --code <authorization-code>
If your version neither completes the callback nor accepts the code, stop and update OpenClaw. Do not work around OAuth by copying credentials into headers.
Probe the live connection
Run a live MCP probe:
openclaw mcp doctor finta --probe
OpenClaw's documentation distinguishes saved configuration from a live probe. The probe should show a reachable Finta server and a discovered tool inventory. A successful status check without a probe is not enough.
Then use a read-only verification prompt:
List the Finta tools available in this session. Use Finta to search its help center for "Aurora MCP." Do not create, update, send, schedule, enroll, or delete anything.
If that works, you can perform an organization-scoped read test with a contact name you are permitted to access:
Search my Finta CRM for the contact I name and show only the matching record summary. Do not change any data.
Review the exact tool name and arguments before approving either call.
Add Finta through the Control UI
OpenClaw's current Control UI guide documents a dedicated MCP page at /mcp.
- Open MCP from the sidebar.
- Add a remote server named Finta.
- Choose Streamable HTTP.
- Enter
https://finta.ai/mcp. - Choose OAuth authentication.
- Save the configuration.
- Use Save & Publish only when you intend the running Gateway to receive the connector.
- Complete OAuth and run
openclaw mcp doctor finta --probefrom the terminal.
A saved Control UI row still requires the same live proof.
Use Finta for relationship work, not blind automation
The value of connecting Finta is not a larger generic tool list. It is access to supported organization context while the relationship record remains in Finta. Depending on your permissions and the current Finta release, available tools may help an agent find CRM contacts, inspect deals, search network contacts, review documents, or prepare a next step.
Start with retrieval. Ask the agent to explain which Finta record or tool supports its answer. Treat a possible relationship path as evidence to review, not permission to request an introduction. Keep external messages, sequence enrollment, destructive changes, and other consequential actions behind explicit review.
See Finta MCP tools reference for the live tool families and Finta MCP security and permissions for Finta's organization and confirmation boundaries.
Troubleshooting OpenClaw and Finta MCP
| Symptom | What to check |
|---|---|
authorization-required | Run openclaw mcp login finta, complete Finta sign-in, then probe again. |
| Browser returns to a dead loopback page | Update to a release containing the callback fix, or copy only the returned authorization code and run openclaw mcp login finta --code <code>. |
| Server is saved but no tools appear | Confirm streamable-http, run openclaw mcp doctor finta --probe, and inspect the reported OAuth state. |
| Tools disappear in a long-running Gateway | Re-run login and probe, then reload or restart the Gateway. Update OpenClaw before diagnosing Finta. |
| The wrong Finta organization is connected | Run openclaw mcp logout finta, repeat login, and select the intended organization. |
| The CLI works but the Gateway does not | Saving CLI configuration does not refresh another running process. Publish the Control UI change or follow the documented Gateway reload path. |
For Finta-specific errors, continue to Troubleshoot a Finta MCP Connection.
Limitations
- OpenClaw controls its CLI, Control UI, Gateway lifecycle, OAuth client behavior, and release cadence.
- The latest stable OpenClaw release and the current main-branch documentation may not describe identical behavior.
- Connecting Finta does not grant access beyond the selected Finta organization and the user's existing permissions.
- A discovered tool may still require credits, another connected data source, or a confirmation step.
- A live MCP probe proves reachability and tool discovery. It does not prove that every Finta action is suitable for autonomous use.
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: Pending an authenticated OpenClaw connection, discovered-tool inventory, and successful read-only Finta tool call receipt on a named stable OpenClaw release.