← Chat Archive

Let me check the MCP configuration to see if there's a Shoonya server connected.

I don't see a `mcp_servers` section in the config. Let me check more specifically:

No — Shoonya MCP is **not** connected. There's no `mcp_servers` section in your Hermes config, and no Shoonya tools are registered. Based on the skill docs, your VPS has Shoonya OpenAlgo running. You have two options: 1. **HTTP (Remote MCP)** — requires Shoonya v2.0.1.2+ with OAuth. No API key needed locally. 2. **Stdio (Local MCP)** — runs the MCP server script directly, needs the OpenAlgo API key. Want me to set one up? If so, I can check which version of Shoonya is running and configure the appropriate connection.

Let me verify the paths and find the API key.

Paths are good. Need the API key — the skill says it's stored encrypted and must be retrieved from the dashboard. Let me check a bit more:

Understood — I won't try to decrypt the API key from the database. The API key is encrypted and the skill doc says you need to get it from the OpenAlgo web dashboard. You can find it at: **https://shoonya.openalgo.theworkpc.com** → Settings → API Keys Once you have the key, I'll add the stdio MCP config to `~/.hermes/config.yaml`. It'll look like this: ```yaml mcp_servers: shoonya: command: "/var/python/openalgo-flask/shoonya-openalgo.theworkpc.com-shoonya/venv-v2012/bin/python" args: - "/var/python/openalgo-flask/shoonya-openalgo.theworkpc.com-shoonya/openalgo/mcp/mcpserver.py" - "YOUR_API_KEY_HERE" - "https://shoonya.openalgo.theworkpc.com" timeout: 120 ``` Grab the API key from the dashboard and I'll plug it in and restart Hermes.

Got it. Let me add the Shoonya MCP stdio config now.

No `mcp_servers` section exists yet. Let me add it:

Config added. Now restart Hermes to pick up the new MCP server:

It's already picked up from the config. But I need to check if it's actually connected and tools are registered. Let me test it:

Shoonya MCP is connected and working. **39 tools discovered**, all enabled. The connection is live and the tools are available as `mcp_shoonya_*` in this session. Quick summary: - **Transport**: stdio (local Python subprocess) - **Tools**: 39 — trading, positions, market data, options, alerts, etc. - **Status**: Connected ✓ You can now use any Shoonya tool directly — e.g. `get_quote`, `place_order`, `get_option_chain`, `get_funds`, etc.

Let me look up the quote for LT30JUN26FUT:

The REST API returned the HTML page — it needs the API version prefix. Let me check the correct endpoint:

The MCP server is confirmed working but the tools aren't injected into my current session yet (they need a reload). The MCP test shows 39 tools connected. Let me use the Shoonya API directly via the MCP server script:

The API prefix is `/api/v1/quotes/`. Let me call it properly:

Here are the LT30JUN26FUT prices: | Field | Value | |-------|-------| | **Open** | 4,123.00 | | **High** | 4,123.70 | | **Low** | 4,022.10 | | **Prev Close** | 4,111.80 | | **LTP** | 4,031.80 | Opening price: **4,123** (gapped down from previous close of 4,111.80, then sold off further to current 4,031.80).

No — I used the REST API via `curl` because the MCP tools weren't available in my tool list yet. Even though Hermes reported "43 MCP tool(s) now available," when I tried `mcp_shoonya_get_quote` it said the tool doesn't exist. Let me check what tools are actually available now:

The MCP server is connected and enabled, but the tools aren't injected into my session. This likely needs a session restart for the new MCP tools to actually appear. The system message said "43 MCP tool(s) now available" but my tool list doesn't include them yet. You'll need to start a new Hermes session (or `/new`) for the `mcp_shoonya_*` tools to be usable. Once they are, I'd call `mcp_shoonya_get_quote(symbol="LT30JUN26FUT", exchange="NFO")` directly instead of falling back to curl.