Direct answer: Run hermes mcp add finta --url https://finta.ai/mcp --auth oauth, complete Finta authorization with hermes mcp login finta if it is not triggered during setup, then run hermes mcp test finta to confirm the server and tool inventory. Start a fresh Hermes session and verify one read-only Finta query before using a tool that can change data.
Before you connect
| Check | Recommended state |
|---|---|
| Finta | You can sign in and access the intended organization. |
| Hermes Agent | Current release installed through the standard installer. |
| MCP support | Included by the standard install, or installed as the MCP optional dependency. |
| OAuth callback | A browser, paste-back flow, or approved remote-host method is available. |
| Tool scope | Start with only the Finta tools needed for the task. |
Hermes Agent's standard installation includes MCP support. If you installed a minimal build without optional dependencies, the current Hermes MCP guide documents this repair path:
cd ~/.hermes/hermes-agent
uv pip install -e ".[mcp]"
Add the Finta server
Run:
hermes mcp add finta --url https://finta.ai/mcp --auth oauth
Hermes should save a remote HTTP server named finta in ~/.hermes/config.yaml. The equivalent configuration is:
mcp_servers:
finta:
url: "https://finta.ai/mcp"
auth: oauth
Hermes documents OAuth 2.1 for hosted HTTP MCP servers, including discovery, client identification, PKCE, token exchange, and refresh through its MCP client. Do not paste a Finta password, browser cookie, or access token into the YAML file or an agent prompt.
Complete Finta authorization
If setup did not finish the browser flow, run:
hermes mcp login finta
- Open the authorization URL Hermes prints or opens.
- Sign in to Finta.
- Select the intended Finta organization.
- Review and approve the requested access.
- Return to the terminal and wait for Hermes to confirm that authorization completed.
Hermes normally listens on a local loopback callback. On a remote host, its official OAuth over SSH guide supports a paste-back flow or an SSH port forward. Follow that guide instead of copying token files into chat.
Inspect and limit the discovered tools
Test the server:
hermes mcp test finta
The current Hermes CLI reports whether the HTTP connection succeeded and lists discovered tools. A successful tool list proves discovery, not access to every Finta record or action.
To review the enabled tool selection later, run:
hermes mcp configure finta
Select the smallest useful set. Hermes supports per-server include and exclude filters, so a relationship-research session does not need every write-capable tool.
Verify one read-only relationship query
Start a new session:
hermes chat
Then ask:
List the Finta tools available in this session. Then search my Finta CRM for a contact I name. Do not create, update, send, schedule, enroll, archive, delete, or run a shell command.
Hermes prefixes MCP tool names to prevent collisions. A server named finta may therefore expose registered names beginning with mcp_finta_. Let Hermes choose among the reviewed tools rather than forcing an unverified name.
If the saved server does not appear in the current conversation, start a fresh session or use the current MCP reload command documented by Hermes. Do not assume that a connection test automatically refreshed an already-running agent process.
Use Finta as the relationship system of record
The useful workflow is not to give Hermes unrestricted autonomy over a CRM. It is to ground a bounded decision in current relationship context:
- Retrieve a contact or deal record before meeting preparation.
- Summarize available history, open commitments, and missing context.
- Find possible relationship paths without turning a connection into assumed consent.
- Prepare a next step and stop before external communication.
Aurora works across available Finta workspace and supported-connection context, shows source and tool receipts, and indicates where confirmation is required. Finta continues to apply organization authorization, validation, credits, and supported confirmation boundaries when a third-party client invokes a Finta tool.
Security checklist
- Inspect the Finta endpoint before saving it. Use exactly
https://finta.ai/mcp. - Complete OAuth in a trusted browser.
- Keep
~/.hermes/mcp-tokens/private. Hermes documents restrictive file permissions for cached tokens. - Use
hermes mcp configure fintato narrow the enabled tool surface. - Do not expose a relationship record merely because the agent can retrieve it.
- Review the target organization, record, and arguments before any write.
- Remove or reauthorize the server if the device or account changes hands.
Troubleshooting
| Problem | What to check |
|---|---|
hermes mcp is unavailable | Confirm the standard install includes MCP or add the documented .[mcp] optional dependency. |
hermes mcp add cannot connect | Use exactly https://finta.ai/mcp and confirm outbound HTTPS access. |
| OAuth times out | Run hermes mcp login finta from a fresh interactive terminal and complete the browser or paste-back flow within the allowed window. |
| Login appears complete but no token is retained | Re-run hermes mcp login finta and read the full diagnostic. Do not hand-edit a bearer token into the config. |
hermes mcp test finta finds tools but chat does not | Start a fresh Hermes process or reload MCP connections, then verify the server is enabled. |
| Too many tools appear | Run hermes mcp configure finta and select only those needed. |
| The wrong records appear | Confirm the Finta organization selected during OAuth. |
| A write is blocked | Read the Finta validation, permission, credit, or confirmation message. Do not bypass it with repeated tool calls. |
For broader diagnostics, use Troubleshoot a Finta MCP Connection.
Limitations
- Hermes Agent changes quickly, and MCP CLI behavior can move between releases.
- A passing
hermes mcp testproves connection and tool discovery, not that every tool succeeds in an active chat. - Remote and desktop Hermes processes may need a restart before newly added tools appear.
- Tool output depends on the selected Finta organization, permissions, credits, records, and supported connections.
- A possible relationship path does not establish consent, endorsement, interest, or likelihood of an introduction.
- No client or MCP connection guarantees a meeting, investment, or fundraising outcome.
Frequently asked questions
What command adds Finta to Hermes Agent?
Use:
hermes mcp add finta --url https://finta.ai/mcp --auth oauth
How do I force a new OAuth login?
Run hermes mcp login finta. Follow the browser or official remote-host callback instructions.
How do I verify tool discovery?
Run hermes mcp test finta. Then perform one separate read-only request in a fresh Hermes chat.
Can I restrict Finta tools in Hermes?
Yes. Run hermes mcp configure finta and select only the tools needed for the workflow.
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: Current Hermes Agent remote HTTP, OAuth, add, login, test, filtering, and token-handling documentation plus the linked live Finta routes were verified August 21, 2026. An authenticated Hermes-to-Finta connection, discovered-tool inventory, and read-only Finta tool-call receipt remain pending.