Sign inGet started

Official YieldCove integration

Your money. Your context.Your choice of agent.

Connect Hermes, Codex or Claude Code to your finances. Ask about your portfolio and spending—or enable writing so your agent can log trades, income and expenses for you.

HermesCodexClaude CodeMCP
  • Choose reading or reading + logging per workspace
  • Review your finances and log records by asking your agent
  • Disconnect whenever you want, from Settings
Connect your agentFollow the visual guide

Included with your free YieldCove account. Your agent may require a separate subscription.

Your YieldCoveRead-only
You

Help me understand how my portfolio is spread out.

Reading your connected workspace

Your sample holdings are concentrated in two funds. I can compare their recorded cost basis and review dividends, keeping CAD and USD separate.

Recorded allocationCAD

VFV.TO70%

XEQT.TO30%

Recorded cost basisCAD 4,000.00
From holdings and dividend history

Illustrative conversation · sample data, not a live account

The short version

Three steps. Then just ask.

You need a YieldCove account with some recorded data and an installed agent that supports remote MCP with bearer authentication. No model API key is needed inside YieldCove.

  1. 01

    Choose what to share

    Open Settings → Agents. Choose the workspaces your agent can read and optionally enable logging. Create a personal key.

    Wheel ✓ Invest ✓ Budget ✓
  2. 02

    Connect once

    Save the key privately. Copy the ready-made configuration into your agent and restart it.

    YieldCove → secure connection → Agent
  3. 03

    Ask a real question

    Try the first prompt. Your agent reads the tools you enabled and explains what it finds.

    “Give me my weekly money review.”
Connect your agent

Made for the agent you use.

Start with Hermes or choose another compatible client. These configurations contain an environment-variable reference, never your actual secret. Merge the entry into your existing configuration; keep your other servers.

Save YIELDCOVE_API_KEY=your-key in your private ~/.hermes/.env file. Merge the configuration below into ~/.hermes/config.yaml, under the existing mcp_servers section if present. Restart Hermes so it discovers the YieldCove tools.

~/.hermes/config.yaml
mcp_servers:
  yieldcove:
    url: "https://yieldcove.com/api/integrations/mcp"
    headers:
      Authorization: "Bearer ${YIELDCOVE_API_KEY}"

Replace “your-key” with the key from Settings. Keep the value in a private environment or secret store—not in chat, source control, screenshots or a shared configuration. Configuration downloads do not include your key.

Agent documentation

Less setup. More useful questions.

Copy a prompt into your connected agent. Enable the matching workspace first. Answers depend on the data you have recorded.

Wheel
Use YieldCove to review my open wheel positions and watchlist. Group upcoming expiries, show recorded premiums and note missing information. Do not place trades.
Invest
Use YieldCove to summarize my holdings, cost basis and recorded dividends this year. Keep currencies separate, identify concentration and distinguish recorded values from live market prices.
Budget
Use YieldCove to review my spending this month and upcoming recurring bills. Page through all relevant transactions, keep currencies explicit and suggest three items I could review. Do not change my records.

Let your agent do the logging, too.

Reading is the default. Each workspace has its own optional writing permission. Wheel can log CSPs and covered calls; Invest can record buys and sells in existing accounts; Budget can record income and expenses. These tools add records to your tracker, not orders or payments.

  1. 01

    Enable only what you need

    In Settings → Agents, check the workspace and its optional logging permission. For an existing key, create a replacement with the new permissions and revoke the old one.

  2. 02

    Give the actual details

    Tell your agent the account, date, symbol and amounts. Wheel premiums are per share, quantities are contracts and opening commission is the total. Invest uses shares and the account’s currency; Budget uses signed amounts.

  3. 03

    Check the saved record

    Your agent receives a record ID. Open the matching workspace to review or correct it. A request UUID prevents duplicate records when the same request is retried; use a new UUID only for a different transaction.

Start a logging conversation
I want to log a trade I already made in YieldCove. First check whether my connection allows logging in the right workspace. Ask me for any missing account, date, symbol, price, premium, quantity or fee details. Summarize the record before saving; use one request UUID and reuse it if a retry is needed. Never place a brokerage order.

What your agent can access

Only tools permitted by the key are exposed. MCP and REST enforce the same workspace and write permissions. Logging requires confirmed: true and a unique request_id (UUID). Agents must ask about missing details and reuse the same UUID and parameters on retries. No operator API, Control Center or publishing access is included.

Wheel

  • list_positions

    Recorded options positions; optional status and ticker filters.

  • list_watchlist

    Watchlist symbols, tags and notes.

  • log_wheel_trade

    Add an executed CSP or covered call to the wheel tracker. Requires optional write permission.

Invest

  • invest_list_accounts

    Accounts and ledger-derived cash.

  • invest_list_holdings

    Holdings and recorded cost basis.

  • invest_portfolio_summary

    Portfolio summary by currency.

  • invest_dividend_summary

    Recorded dividends for a chosen year.

  • log_invest_trade

    Record a buy or sell in an existing investment account. Requires optional write permission.

Budget

  • budget_overview

    Monthly cashflow, budget and upcoming bills.

  • budget_list_accounts

    Budget accounts and recorded balances.

  • budget_list_transactions

    Paginated spending and income, with date filters.

  • budget_list_recurring

    Recurring bills and unlogged occurrences.

  • budget_list_goals

    Savings goals and progress.

  • log_budget_transaction

    Record income or an expense in an existing budget account. Requires optional write permission.

For custom agents: REST API reference

Send your personal key in the Authorization: Bearer header. GET returns a connection check and the allowed tools, including their JSON input schemas. POST calls one tool. Use an HTTPS-capable client; browser-only clients on other origins are not supported.

Test key
curl --fail-with-body 'https://yieldcove.com/api/integrations/agent' \
  -H "Authorization: Bearer $YIELDCOVE_API_KEY"
Example: a page of budget transactions
curl --fail-with-body 'https://yieldcove.com/api/integrations/agent' \
  -H "Authorization: Bearer $YIELDCOVE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{"action":"budget_list_transactions","parameters":{"limit":25,"offset":0}}'

POST accepts {action, parameters} and returns {ok: true, data}. Parameters are validated; unknown fields are rejected. Use the GET manifest as the exact parameter reference. Errors: 400 invalid parameters, 401 invalid/expired/revoked key, 403 denied tool, 404 missing record, 413 oversized request, 429 rate limit, 503 unavailable. Limit: 60 requests per minute per key, 16 KB request bodies. Honor Retry-After on 429. Transaction pages support limit (1–200) and offset; positions return at most 500 newest entries. A write returns its record ID and replayed flag. Generate one request_id UUID per real transaction; retain it on retries. Reusing it with changed details returns 409 request_id_conflict. Use the returned ID to review the record in the app.

Helpful context. Clear boundaries.

You choose read-only access or reading plus logging per workspace. Logging can add wheel trades, Invest buys/sells and Budget income/expenses. It cannot edit or delete existing records, execute brokerage orders, pay bills, synchronize bank accounts or publish content. Correct records in the app. Ledger warnings, currency differences and missing data still matter.

You choose the access

Each key belongs to one account. Reading and logging permissions are selected per workspace; existing keys stay read-only. Create a replacement to change access. Keys expire after 30 or 90 days.

Know where your data goes

Your agent provider receives requested data under its privacy policy. YieldCove stores a key digest, connection metadata and write receipts (action, record ID and request hash), never the raw key or agent conversations.

A clear off switch

Revoke a connection in Settings → Agents to block subsequent requests, including existing MCP clients. Revocation cannot erase data already received by an agent or cancel a request already in progress.

A little help, if you need it.

My key test fails or I get a 401.

Check for extra spaces, an expired key or a revoked connection. The key starts with yc_live_. Set YIELDCOVE_API_KEY in the environment your agent actually uses. If you lost the key, create a new connection and revoke the old one.

My agent connects but cannot see a workspace.

Check the key’s workspace and logging permissions in Settings. For more access, create a replacement key, update your agent’s private credentials and restart it. Existing read-only keys never gain write access automatically.

The answer is empty or does not match what I expected.

Check that you created the key in the correct YieldCove account and that the workspace contains data. Ask your agent to check dates, archived accounts, currencies and transaction pagination. Recorded cost basis is not a live portfolio valuation.

Can I use this in any chatbot?

The agent must support remote MCP with custom bearer authentication, or be able to call an authenticated REST API. Hermes, Codex and Claude Code have setup examples above. OAuth-only connector screens cannot use this personal-key setup. YieldCove does not include an AI model subscription.

How do I renew or remove a connection?

Create a new key, update the agent’s private credentials and verify it, then revoke the old key in Settings. Revoke an exposed key immediately. Use a separate key for each agent so you can disconnect them independently.

“Official” means built and maintained by YieldCove. Compatibility does not imply endorsement, marketplace approval or a partnership with Nous Research, OpenAI or Anthropic.