MCP Server Endpoint

Model Context Protocol (MCP) server endpoint for AI agent integration.

Connect any MCP compatible AI client (Claude, GPT, Cursor, Windsurf, or custom agents) to the full Bavest API through a single MCP server URL. Once connected, all Bavest API endpoints are available as MCP tools, no individual endpoint wiring required.

Quick Start

Add the following to your MCP client configuration:

{
  "mcpServers": {
    "bavest": {
      "type": "url",
      "url": "https://api.bavest.co/v2/mcp?api_key=YOUR_API_KEY"
    }
  }
}

Available Tools

Once connected, the MCP server exposes all Bavest API endpoints as callable tools:

CategoryTools
EquitiesProfile, financials, balance sheets, cash flows, metrics, peers, market cap
ETFsProfile, holdings, sectors, countries, risk, fees, KID documents
FundsProfile, holdings, sectors, countries, performance
CryptoQuotes, listings
ForexQuotes, candles
TimeseriesReal time quotes, EOD prices, historical candles, NAV
DividendsHistory, annual summaries, calendar
EstimatesConsensus, price targets, recommendations, upgrades and downgrades
Corporate ActionsEarnings, transcripts, splits
Economic IndicatorsCPI, GDP, inflation, interest rates, unemployment
NewsStock specific and market wide news
ReferenceSecurity search, screener, index lists
Bavest QuantOSPortfolio allocation, stats, returns, charts
CalendarEarnings, IPOs, splits, AGMs
BulkBatch any endpoint across up to 100 symbols

Supported Clients

Any client implementing the Model Context Protocol specification can connect, including:

ClientConfig location
Claude Desktopclaude_desktop_config.json
Claude Code.claude/settings.json
Cursor.cursor/mcp.json
Windsurf.windsurf/mcp.json
Custom agentsDepends on implementation

Authentication

Pass your API key as the api_key query parameter on the MCP server URL. The x-api-key header is also supported for clients that allow custom headers.

Query Params
string
required

Your Bavest API key. Obtain from bavest.co/dashboard.

Body Params

JSON-RPC 2.0 request following the MCP specification.

string
enum
required

JSON-RPC protocol version

Allowed:
string

Request identifier (omit for notifications)

string
enum
required

MCP method to invoke

Allowed:
params
object

Method parameters (varies by method)

Headers
string
enum
Defaults to application/json

Response content type. Only application/json is supported.

Allowed:
Responses

Language
Credentials
Header
URL
Request
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json