Provides unified access to Akshare data interfaces via MCP, converting multiple financial data endpoints into a standard MCP tool format.
Configuration
View docs{
"mcpServers": {
"august1996-mcp-akshare": {
"command": "uvx",
"args": [
"mcp-akshare_dir"
]
}
}
}This MCP server converts AkShare data interfaces into a standardized MCP tool format, enabling you to call diverse financial data interfaces through a unified API. It makes it easier to access multiple data sources from AkShare via a consistent MCP client workflow.
You run the MCP server locally or remotely and connect to it with an MCP client. Use the standard MCP runtime to execute the server and access AkShare data through the unified MCP interface. You can start from a local path or a published MCP entry point, then issue data requests to AkShare through the MCP layer.
Prerequisites: you need Python development tooling and the MCP runtime in your environment. The server can be run by pointing the MCP runtime at the AkShare-based project directory.
Step 1. Clone the project repository.
Step 2. Start the MCP server using the provided runtime configuration. You have two equivalent runtime options shown here. Choose one to run the server.
The server exposes two MCP configurations you can use directly: one targets the built-in MCP entry for the project, and the other targets the local development path. Both use the same runtime, but point to different sources.
Converts Akshare data endpoints into MCP tool format for uniform access.
Provides a single API surface to call multiple Akshare data interfaces.
Supports multiple Akshare data endpoints through a common MCP client.