FUTURESCME contracts
Featured Firm VestVest 5% OFF all plans · from $10 · NQ 50x · no swap fee · USDC payouts on-chain 5% Off Code JMU

VERSION HISTORY

MCP Server

My Funded Perpetuals·5 versions·Read the live article ↗·Rule Radar


CompareA: Version 4againstB: Version 5Pick A and B on any two versions below.
Track a rule
Fetches the article and compares it with Version 5.
▸Version 5November 12, 2026, 4:08 AM+1−1

Changes shown against Version 4.

MCP Server
+ Source: https://docs.myfundedperpetuals.com/mcp-server
Connect AI assistants and agents to the MyFundedPerps REST API through the hosted Model Context Protocol server.
What is the MCP server?
Errors and rate limits. A rejected request returns
status 429 with a Retry-After header and is always safe to retry.
− This documentation is built and hosted on Mintlify, a developer documentation platform.

SHA-256 22a96486c7200a60dae2284385abaefb5f3c04022e5eed20142807792d904194

▸Version 4November 11, 2026, 5:58 PM+1−1

Changes shown against Version 3.

MCP Server
− Source: https://docs.myfundedperpetuals.com/mcp-server
Connect AI assistants and agents to the MyFundedPerps REST API through the hosted Model Context Protocol server.
What is the MCP server?
Errors and rate limits. A rejected request returns
status 429 with a Retry-After header and is always safe to retry.
+ This documentation is built and hosted on Mintlify, a developer documentation platform.

SHA-256 f872b5b47dfa1456fd0c71a47c53d105745ebc24ee90cd845eb89d24603a8340

▸Version 3October 25, 2026, 3:47 AM+3−3

Changes shown against Version 2.

Ceiling5 active sessions; a new approval revokes the oldest
[!NOTE]
− API keys are for direct REST API and SDK calls, not for MCP. A live fp_live_
− key sent to the MCP server is refused with a prompt to sign in with OAuth, and
− an MCP session cannot be replayed against the REST hosts.
+ API keys are for direct REST API calls, not for MCP. A live fp_live_ key
+ sent to the MCP server is refused with a prompt to sign in with OAuth, and an
+ MCP session cannot be replayed against the REST hosts.
Sandbox
The sandbox has no OAuth flow. To point an MCP client at your

SHA-256 22a96486c7200a60dae2284385abaefb5f3c04022e5eed20142807792d904194

▸Version 2October 20, 2026, 4:45 PM+2−0

Changes shown against Version 1.

under your own session, so everything in Idempotency and
Errors and rate limits applies unchanged.
+ [!WARNING]
Tools placed under an AI assistant's control can cancel orders and close
positions. Configure the client to request the read scope when the assistant
Expiry90 days after approval
Ceiling5 active sessions; a new approval revokes the oldest
+ [!NOTE]
API keys are for direct REST API and SDK calls, not for MCP. A live fp_live_
key sent to the MCP server is refused with a prompt to sign in with OAuth, and

SHA-256 f98e4ff135428183105d98a11d08ae2e9394e7bb9e9a3594381c80e5f9075204

▸Version 1October 11, 2026, 2:36 PM

First archived version.

MCP Server
Source: https://docs.myfundedperpetuals.com/mcp-server
Connect AI assistants and agents to the MyFundedPerps REST API through the hosted Model Context Protocol server.
What is the MCP server?
The Model Context Protocol (MCP) is an open standard that lets AI
applications such as Claude, Claude Code, and other MCP-capable agents call
external APIs as tools. MyFundedPerps hosts an MCP server that exposes
the REST trading and read operations as tools, so an assistant can list your challenge
accounts, quote markets, place and manage orders, and inspect positions and
fills on your behalf.
The server speaks the current stateless MCP revision (2026-07-28) over
Streamable HTTP:
https://mcp.myfundedperpetuals.com
There is nothing to install or run yourself. You sign in through OAuth in
your browser, and each tool call then runs as one authenticated REST request
under your own session, so everything in Idempotency and
Errors and rate limits applies unchanged.
Tools placed under an AI assistant's control can cancel orders and close
positions. Configure the client to request the read scope when the assistant
only needs to observe, and prefer a sandbox key while you evaluate an agent.
Documentation and connection URLs
This guide is at /mcp-server on the documentation site. The documentation
site's /mcp path belongs to Mintlify's documentation-search service and can
return 401 Unauthorized when opened in a browser. Use
https://mcp.myfundedperpetuals.com in your trading MCP client.
See API capabilities for the supported operations and
features that still require the website.
Sign in with OAuth
OAuth is the sign-in method for the MCP server. There is no key to copy:
connect the server and your MCP client opens a browser page where you review
what the client is asking for and approve it with your normal MyFundedPerps
sign-in.
1. Add the server to your MCP client (examples below) and start it.
2. The client discovers the authorization flow automatically and opens
myfundedperpetuals.com/mcp/auth in your browser.
3. Review the client name, access level, and expiry, then choose Approve.
4. The client receives its own session and starts calling tools.
Sessions minted this way:
PropertyValue
AccessTrade on all accounts, or read-only if the client requests read
Expiry90 days after approval
Ceiling5 active sessions; a new approval revokes the oldest
API keys are for direct REST API and SDK calls, not for MCP. A live fp_live_
key sent to the MCP server is refused with a prompt to sign in with OAuth, and
an MCP session cannot be replayed against the REST hosts.
Sandbox
The sandbox has no OAuth flow. To point an MCP client at your
sandbox accounts, send an fp_test_ key as a bearer header
instead (created in
API Key Settings
under the Test environment):
Authorization: Bearer fp_test_...
Connect a client
Claude Code
bash theme={null}
claude mcp add --transport http funding-perpetuals
https://mcp.myfundedperpetuals.com
The first tool use prompts the OAuth sign-in in your browser.
Other MCP clients
Any client that supports Streamable HTTP with OAuth can connect:
json theme={null}
{
"mcpServers": {
"funding-perpetuals": {
"type": "http",
"url": "https://mcp.myfundedperpetuals.com"
}
}
}
Clients register themselves automatically: the server supports both Client ID
Metadata Documents and Dynamic Client Registration, so no manual client setup
is needed. For sandbox testing, add the Authorization header with an
fp_test_ key instead.
Tools
The two CLI authentication endpoints are excluded
because MCP uses its own OAuth flow. Each exposed operation is one tool, named
after the matching
fperp CLI command: list-accounts, get-market-quote,
create-order, cancel-order, close-position, and so on. Tool arguments
use the same snake_case names as the REST API's path, query, and body fields,
and each tool's schema includes nested objects and arrays, required fields,
enums, and numeric constraints. Protective-exit batches expose the complete
expected_orders snapshot and the cancel, modify, and place operation shapes,
including OCO pairing. The REST API still enforces trading rules and current
account state.
Results are JSON with three parts:
FieldMeaning
statusThe HTTP status of the underlying REST call
request_idThe X-Request-Id of the call, for support and debugging
bodyThe REST response, including data or the API error envelope
Failed calls are reported as tool errors carrying the standard error envelope
with error.code and per-field error.details, so an agent can correct its
input and retry. Responses with status 429 include retry_after_seconds.
Idempotency and bulk operations
Tools for operations that require an Idempotency-Key header require an
idempotency_key argument. Generate a UUID or other unique printable ASCII key
(up to 128 characters) and persist it with the exact arguments **before the
first call**. Missing, empty, whitespace-only, or malformed keys are rejected
before an upstream request is sent. The server echoes your key in the result.
Clients that previously omitted this argument must now supply it.
Retry a lost response with the same key, identical arguments, and the same
credential. Never generate a replacement key for an uncertain outcome: that
starts a new operation and can create duplicate exposure. Reconcile ordinary
orders through client_order_id when available. See Idempotency
for the endpoint's replay behavior.
Bulk operations (cancel-all-account-orders, close-all-account-positions)
can return status 202 while work remains. Retain the original arguments and
key, wait for retry_after_seconds, then repeat the call to advance it.
All trading writes advertise destructiveHint: true and
idempotentHint: false. These conservative hints cover both exposure changes
and removal or replacement of protective orders. An HTTP PUT method alone
does not make a mutable exit batch safe to repeat. For writes without an
idempotency key, read current state and reconcile an uncertain outcome before
submitting another write. Read tools advertise read-only and idempotent hints.
Rate limits
The MCP host applies the same per-address limit as the REST hosts: about 300
requests per minute from one source IP address. Account-wide cancel and close
operations share the budgets described in
Errors and rate limits. A rejected request returns
status 429 with a Retry-After header and is always safe to retry.

SHA-256 7d6258184c797fd05f709d05abc920b7b0c49dec7cb0976037341065f291568b

Scroll to Top