Fyers MCP Server

A comprehensive MCP server that enables Claude Desktop to interact with Fyers trading platform through a secure, automated authentication flow.

Local serverstdioPython

What is the Fyers MCP server?

Fyers MCP server exists for a simple reason — assistants are far more useful when they can act on Fyers directly instead of describing what you should do. A comprehensive MCP server that enables Claude Desktop to interact with Fyers trading platform through a secure, automated authentication flow. Supports all major trading operations including portfolio management, order placement, and.

What the assistant can call

Once Fyers is connected, these are the calls the assistant has available:

  • Prerequisites — The Prerequisites tool exposed by this server
  • Testing — The Testing tool exposed by this server

Configuration and credentials

You will need 7 environment variables: PYTHONWARNINGS, LOG_LEVEL, FYERS_CLIENT_ID, YOUR_APP_ID, FYERS_SECRET_KEY, YOUR_SECRET_KEY, ORDER_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Fyers's toolset — Prerequisites, Testing — is a fair guide to whether it matches your workflow. It is maintained by quantabox; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the fyers mcp server does with a few real requests.

Available tools

ToolWhat it does
PrerequisitesThe Prerequisites tool exposed by this server.
TestingThe Testing tool exposed by this server.

How to install the Fyers MCP server

{
  "mcpServers": {
    "fyers-mcp-server": {
      "command": "uv",
      "args": [
        "run", 
        "--directory",
        "/path/to/fyers-mcp-server",
        "python",
        "fyers_mcp_complete.py"
      ],
      "env": {
        "PYTHONWARNINGS": "ignore"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
PYTHONWARNINGSConfiguration value read at startup.Optional
LOG_LEVELConfiguration value read at startup.Optional
FYERS_CLIENT_IDConfiguration value read at startup.Optional
YOUR_APP_IDConfiguration value read at startup.Optional
FYERS_SECRET_KEYCredential the server authenticates with.Yes
YOUR_SECRET_KEYCredential the server authenticates with.Yes
ORDER_IDConfiguration value read at startup.Optional

Example prompts to try

  • Use Fyers to Prerequisites.
  • Use Fyers to Testing.

Frequently asked questions

It connects Fyers to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Prerequisites, Testing) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Fyers directly.