Twelve Data Mcp Server

Created By
twelvedataa year ago
Overview

what is Twelve Data MCP Server?

The Twelve Data MCP Server provides seamless integration with the Twelve Data API, allowing users to access financial market data, including historical time series, real-time quotes, and instrument metadata for stocks, forex pairs, and cryptocurrencies.

how to use Twelve Data MCP Server?

To use the Twelve Data MCP Server, you need to obtain an API key from Twelve Data, which involves creating an account and copying the API key from your dashboard. You can then use various tools provided by the server to fetch data.

key features of Twelve Data MCP Server?

  • Access to historical price data for various financial instruments.
  • Real-time price quotes for stocks, forex, and cryptocurrencies.
  • Metadata retrieval for available stocks, forex pairs, and cryptocurrencies.
  • Easy integration with tools like Claude Desktop and VS Code.

use cases of Twelve Data MCP Server?

  1. Retrieving historical stock prices for analysis.
  2. Getting real-time forex quotes for trading decisions.
  3. Accessing cryptocurrency metadata for investment research.

FAQ from Twelve Data MCP Server?

  • How do I obtain an API key?

You can obtain an API key by signing up at the Twelve Data website and copying it from your dashboard.

  • Is there a cost associated with using the API?

Access to specific endpoints may vary based on your subscription plan with Twelve Data.

  • Can I use this server with Docker?

Yes! You can build and run the server using Docker with the provided commands.

Server Config

{
  "mcpServers": {
    "twelvedata-remote": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.twelvedata.com/mcp/",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "apikey YOUR_API_KEY"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
twelvedata
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 minutes ago