Oanda MCP Server

Created By
BJLG-92a year ago
Oanda MCP Server for Claude
Overview

what is Oanda MCP Server?

Oanda MCP Server is a REST API server designed for Oanda trading operations, deployed on Railway and compatible with Model Context Protocol (MCP).

how to use Oanda MCP Server?

To use the Oanda MCP Server, you need to set up your environment variables with your Oanda API key and account ID, and then you can interact with the API endpoints to manage your trading operations.

key features of Oanda MCP Server?

  • Account information retrieval
  • Position management
  • Order placement (market and limit orders)
  • Current price data
  • Historical data
  • Order cancellation

use cases of Oanda MCP Server?

  1. Automating trading strategies using the API.
  2. Retrieving account and position information for analysis.
  3. Placing and managing orders programmatically.

FAQ from Oanda MCP Server?

  • What is required to use the Oanda MCP Server?

You need an Oanda API key and account ID to access the server.

  • Can I use this server for live trading?

Yes, you can set the environment variable to 'live' for real trading operations.

  • Is there a limit to the number of requests I can make?

The limits depend on your Oanda account type and API usage policy.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
BJLG-92
Star
0
Language
Python
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)

a day ago