Skip to content
InsightsSpeak with us

Resources

Nasu Capital MCP

MCP is an open standard that lets AI assistants connect to external tools and services. Point any compatible client at the Nasu Capital server, authenticate once, and your AI can query the fund directly.

What this does

The Nasu Capital MCP server lets an approved AI assistant answer questions about the fund on your behalf. Connect it once to the client you already use, and you can ask in plain English instead of opening the dashboard.

Built on the open Model Context Protocol standard, so it works with Claude, Cursor, VS Code, and any other MCP-compatible assistant.

"What is the current NAV?" · "How did the fund perform last quarter?" · "Generate a fund report for Q1 2026."

Who this is for

Access is limited to Nasu Capital personnel and approved counterparties. It is not a public API, there is no self-service sign-up, and a connection cannot be established without credentials issued from inside the platform.

  • Access to the Nasu Capital dashboard
  • An MCP key, issued from Settings → MCP. Copy it when it is created — it is shown only once.
  • An MCP-compatible AI client (see the setup guides below)
Your key is a credential. Store it the way you would a password, never commit it to a repository or paste it into a shared document, and have it revoked immediately if a device holding it is lost.

Server URL

The same endpoint is used by every client:

https://api.nasucapital.com/mcp

Authentication

There are two ways to authenticate, and which one you use depends only on what your client supports. Both carry the same access — neither one grants more than the other.

  • Sign-in prompt. Clients that support it will open a Nasu Capital approval screen when you connect. Approve there and the client stores the connection itself — nothing to configure.
  • Header. Clients configured from a file take the key directly as an Authorization header — pick your client below and the exact snippet is shown for you.

Once connected, your assistant will show you which tools it can call. That list reflects your own key — two people can connect the same way and see different capabilities.

Connect your assistant

Pick your client below. Where a key is shown as <your-mcp-key>, paste your own in its place, keeping the word Bearer and the single space in front of it.

Open Settings → Connectors → Add custom connector and enter the details below. Leave the OAuth Client ID and Client Secret fields blank — Claude signs itself in, and your key belongs on the approval screen only. Sign in to the dashboard first, or the approval step stalls after login.

Name:  Nasu Capital
URL:   https://api.nasucapital.com/mcp

Any other client

Anything that speaks MCP over HTTP will work. Point it at the server URL above and give it the Authorization header shown in the examples; clients that prefer a sign-in prompt will find it on their own.

Restart the client after editing a config file — most only read it at startup.

How access is protected

  • Read-only. A connected assistant can look things up and produce reports. It cannot move money, change records, or alter anything about the fund or an investor.
  • Personal details are withheld. Investor identities are masked before anything leaves the platform, and contact and payment information is never included at all — an assistant cannot retrieve it because it is never sent.
  • Keys are limited. Every key is issued to a named person, can be restricted to only part of what the server offers, and expires on a schedule set when it is created.
  • Everything is logged. Each request is recorded against the key that made it, so activity can be reviewed at any time from the dashboard.
  • Revocable instantly. Revoking a key from Settings → MCP cuts off every client holding it, immediately.
Generated reports are delivered to the dashboard, not to the assistant. The file contents never pass through the AI client.

Troubleshooting

The connection is refused or the key is rejected

Confirm the key was issued for MCP under Settings → MCP and has not expired or been revoked. Keys are shown only once, so if there is any doubt about a copy-paste, have a new one issued rather than retrying the old one.

Claude cannot complete the connection

Leave the OAuth Client ID and Client Secret fields blank, sign in to the dashboard before approving, and check the URL matches the one above exactly, with no trailing slash.

An editor or CLI client does not connect

  • Check the header reads Bearer <your-mcp-key> — capital B, one space, key pasted whole.
  • Make sure the config file is valid JSON and in the location named in the guide above.
  • Fully quit and reopen the client; most read their config only at startup.

Something is missing, or a request is declined

Keys can be issued with reduced access, so a colleague may see options you do not. If you need something your key cannot reach, ask an administrator to issue one with the access you need rather than sharing theirs.

Investor names appear abbreviated

That is intended. Identities are masked before data leaves the platform and there is no setting that turns it off.

Last updated: July 2026 · Questions about access? Contact your Nasu Capital administrator.