Octagon: MCP for Public & Prediction Markets Intelligence

The Octagon MCP server provides specialized AI-powered financial research and analysis by integrating with the Octagon Market Intelligence API, enabling users to analyze and extract insights from public filings, earnings calls, financial metrics, stocks & crypto data, stock news, and prediction markets news & research within Claude Desktop and other popular MCP clients.

Tools

✅ octagon-agent orchestrates broad market intelligence analysis

• Public market insights: SEC filings (10-K, 10-Q, 20-F, 8-K, S-1, 13-F, DEF 14A), earnings call transcripts
• Stocks & crypto market data: stock trading, crypto trading data, news, press release, ownerships and holdings

✅ octagon-deep-research-agent for comprehensive deep research

• Multi-source synthesis for investment research questions
• Best for up-to-date, cross-source thematic analysis

✅ Prediction market research tooling

• octagon-prediction-markets-agent for updated research reports on each prediction markets
• prediction_markets_history for structured historical market data retrieval

✅ Live Octagon documentation access

• octagon-docs-search, octagon-docs-read, octagon-docs-list, and octagon-docs-refresh
• MCP resources for octagon-docs://catalog, octagon-docs://status, and octagon-docs://page/{target}

Get Your Octagon API Key

To use Octagon MCP, you need to:

1. Sign up for a free account at Octagon
2. After logging in, from left menu, navigate to API Keys
3. Generate a new API key
4. Use this API key in your configuration as the OCTAGON_API_KEY value

Prerequisites

Before installing or running Octagon MCP, you need to have npx (which comes with Node.js and npm) installed on your system.

Mac (macOS)

1. Install Homebrew (if you don't have it):

   /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
   

2. Install Node.js (includes npm and npx):

   brew install node
   

   This will install the latest version of Node.js, npm, and npx.

3. Verify installation:

   node -v
   npm -v
   npx -v
   

Windows

1. Download the Node.js installer:
   • Go to https://nodejs.org/ and download the LTS version for Windows.
2. Run the installer and follow the prompts. This will install Node.js, npm, and npx.
3. Verify installation: Open Command Prompt and run:

   node -v
   npm -v
   npx -v
   

If you see version numbers for all three, you are ready to proceed with the installation steps below.

Installation

Running on Claude Desktop

To configure Octagon MCP for Claude Desktop:

1. Open Claude Desktop
2. Go to Settings > Developer > Edit Config
3. Add the following to your claude_desktop_config.json (Replace your-octagon-api-key with your Octagon API key):

{
  "mcpServers": {
    "octagon-mcp-server": {
      "command": "npx",
      "args": ["-y", "octagon-mcp@latest"],
      "env": {
        "OCTAGON_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

4. Restart Claude for the changes to take effect

Running on Cursor

Configuring Cursor Desktop 🖥️ Note: Requires Cursor version 0.45.6+

To configure Octagon MCP in Cursor:

1. Open Cursor Settings
2. Go to Features > MCP Servers
3. Click "+ Add New MCP Server"
4. Enter the following:
   • Name: "octagon-mcp" (or your preferred name)
   • Type: "command"
   • Command: env OCTAGON_API_KEY=your-octagon-api-key npx -y octagon-mcp

If you are using Windows and are running into issues, try cmd /c "set OCTAGON_API_KEY=your-octagon-api-key && npx -y octagon-mcp"

Replace your-octagon-api-key with your Octagon API key.

After adding, refresh the MCP server list to see the new tools. The Composer Agent will automatically use Octagon MCP when appropriate, but you can explicitly request it by describing your investment research needs. Access the Composer via Command+L (Mac), select "Agent" next to the submit button, and enter your query.

Running with npx

env OCTAGON_API_KEY=your_octagon_api_key npx -y octagon-mcp

Manual Installation

npm install -g octagon-mcp

Documentation

For comprehensive documentation on using Octagon agents, please visit our official documentation at: https://octagonai.co/docs/

The documentation includes:

• Detailed API references
• Agent-specific query guidelines
• Examples and use cases
• Best practices for investment research

For the latest hosted MCP client setup guide, see:

• Octagon MCP Server Guide
• Octagon Claude Plugin Guide
• Octagon Agents Guide

This MCP server also exposes the live docs corpus directly to MCP clients. Documentation access is fetched from the public Octagon docs LLM entry point at https://octagonai.co/docs/llms.txt; it does not use or transmit OCTAGON_API_KEY.

Available Tools

The MCP server currently exposes the following tools:

Documentation Tools

These tools expose live Octagon docs inside the MCP session. They work even before OCTAGON_API_KEY is configured, which makes them useful for setup, troubleshooting, and discovering the right Octagon agent or API workflow.

octagon-docs-list

Lists live docs sections and pages from the Octagon docs corpus.

Parameters

• section (string, optional): filter by docs section.
• source (docs, site, or all, optional): defaults to the docs corpus.
• limit (number, optional): maximum entries to return.

octagon-docs-search

Searches the Octagon API, agent, MCP, and plugin docs with source URLs and optional snippets.

Parameters

• query (string, required): search query.
• section (string, optional): filter by docs section.
• source (docs, site, or all, optional): defaults to the docs corpus.
• limit (number, optional): maximum results to return.
• includeSnippets (boolean, optional): include matched snippets in results.

Example:

Search Octagon docs for Claude plugin connector setup.

octagon-docs-read

Reads one docs page or section as Markdown by title, URL, path, or catalog id.

Parameters

• target (string, required): docs title, URL, path, or catalog id.
• source (docs, site, or all, optional): defaults to the docs corpus.
• maxChars (number, optional): maximum Markdown characters to return.
• preferCachedContent (boolean, optional): use the indexed docs corpus when available.

Example:

Read the Octagon MCP server guide.

octagon-docs-refresh

Refreshes the in-memory docs catalog from the live LLM-friendly docs endpoints.

Parameters

• includeSite (boolean, optional): also refresh the broader https://octagonai.co/llms.txt site index.

Documentation Resources

Clients that support MCP resources can also browse:

• octagon-docs://catalog: normalized live docs catalog.
• octagon-docs://status: cache state, source endpoints, and refresh metadata.
• octagon-docs://page/{target}: one docs page or section as Markdown.

octagon-agent

Orchestrates public and private market intelligence analysis.

Parameters

• prompt (string, required): natural language research request.
• conversation (string, optional): existing Octagon conversation ID to continue a prior octagon-agent thread. Omit this on the first turn.
• newConversation (boolean, optional): if true, starts a fresh Octagon thread for the active session/thread anchor. Recommended for the first turn of a brand new visible chat in top-layer hosts such as Claude Desktop.

Threaded usage

octagon-agent is the only MCP tool that forwards Octagon conversation threading. It is a stateful tool and expects session continuity. The MCP resolves session/thread state in this order:

1. stored conversation for MCP transport session identity, when the transport actually provides it
2. stored conversation for the server-managed default stdio session
3. explicit conversation can still override the active session conversation for that call

This package currently runs as a stdio MCP server. In stdio mode, the server automatically establishes a process-local session for continuity across calls. Most local hosts such as Claude Desktop or Cursor can therefore use octagon-agent without supplying any extra threading fields for basic follow-up behavior.

When a top-layer host knows a call is the first turn of a new visible chat, it should pass newConversation: true. That explicitly clears any stored Octagon thread for the active MCP session anchor before the call, which prevents stale continuity when a stdio host reuses the same long-lived MCP process across multiple visible chats.

This means you can use any of these patterns:

1. First call: send only prompt
2. Let the MCP host preserve transport session continuity or rely on the default stdio session
3. Second call: either
   • send the new prompt in the same MCP session, or
   • keep using the same stdio MCP process, or
   • explicitly pass the previous conversation

Transport session identity is the canonical continuity primitive for standards-compliant stateful MCP transports. For local stdio usage, the server-managed process session provides default continuity.

Session identity and Octagon conversation identity are different concepts:

• MCP session identity controls server-side cont