Futuur API
STDIOFutuur API下注操作集成的MCP服务器
Futuur API下注操作集成的MCP服务器
Futuur API MCP Integration is a powerful TypeScript-based server that implements the Model Context Protocol (MCP) for seamless integration with the Futuur API. This project provides a robust interface for handling market data, categories, user information, and betting operations.
For Claude Desktop:
npx -y @smithery/cli install @futuur/futuur-mcp --client claude
For Cursor:
npx -y @smithery/cli install @futuur/futuur-mcp --client cursor
If you prefer to install manually:
git clone https://github.com/yourusername/futuur-api-mcp.git cd futuur-api-mcp
npm install
futuur-api-mcp/
├── src/
│   ├── tools/          # Tool implementations
│   ├── utils/          # Utility functions
│   └── index.ts        # Main server entry point
├── build/              # Compiled JavaScript output
├── package.json        # Project dependencies
├── package-lock.json   # Dependency lock file
├── tsconfig.json       # TypeScript configuration
└── .env               # Environment variables
The project uses TypeScript for type safety and better development experience. The server implements the Model Context Protocol (MCP) using the official SDK.
The server includes a debug mode that can be toggled by setting the DEBUG constant in index.ts. When enabled, it provides detailed logging information.
@modelcontextprotocol/sdk: Core MCP implementationzod: Runtime type checking and validationTo integrate the MCP server with Cursor, follow these steps:
npm run build
Windows:
cmd /c npx mcprunner FUTUUR_PUBLIC_KEY=*YOUR_FUTUUR_PUBLIC_KEY* FUTUUR_PRIVATE_KEY=*YOUR_FUTUUR_PRIVATE_KEY* -- node C:/webapps/futuur-api-mcp/build/index.js
macOS/Linux:
npx mcprunner FUTUUR_PUBLIC_KEY=*YOUR_FUTUUR_PUBLIC_KEY* FUTUUR_PRIVATE_KEY=*YOUR_FUTUUR_PRIVATE_KEY* -- node C:/webapps/futuur-api-mcp/build/index.js
Make sure to replace *YOUR_FUTUUR_PUBLIC_KEY* and *YOUR_FUTUUR_PRIVATE_KEY* with your actual Futuur API credentials.
ISC
Contributions are welcome! Please feel free to submit a Pull Request.
For support, please open an issue in the GitHub repository or contact the development team.