Fanvue MCP Server
A Model Context Protocol (MCP) server for the Fanvue API.
Installation
pip install fanvue-mcp
Or use with uvx (no installation required):
uvx fanvue-mcp
Usage
To run the server, you need to provide your Fanvue OAuth credentials. You can obtain these by creating an application in the Fanvue Developer Portal.
Running the Server
export FANVUE_CLIENT_ID="your_client_id"
export FANVUE_CLIENT_SECRET="your_client_secret"
# Run the server
fanvue-mcp
The server will start at http://0.0.0.0:8080 with the following endpoints:
- MCP Endpoint:
http://localhost:8080/mcp - SSE Endpoint:
http://localhost:8080/sse - Health Check:
http://localhost:8080/health
Connecting to MCP Clients
Cursor
- Open Cursor Settings (
Cmd/Ctrl + Shift + Jor Settings UI). - Navigate to Features > MCP.
- Edit your MCP settings JSON and add:
{
"mcpServers": {
"fanvue": {
"command": "uvx",
"args": ["fanvue-mcp"],
"env": {
"FANVUE_CLIENT_ID": "your_client_id",
"FANVUE_CLIENT_SECRET": "your_client_secret"
}
}
}
}
Cursor will automatically start and manage the server process.
Claude Code (VS Code Extension)
- Open VS Code Settings (
Cmd/Ctrl + ,). - Search for "MCP" or navigate to Extensions > Claude Code.
- Edit the MCP configuration (usually in
settings.json):
{
"claude.mcpServers": {
"fanvue": {
"command": "uvx",
"args": ["fanvue-mcp"],
"env": {
"FANVUE_CLIENT_ID": "your_client_id",
"FANVUE_CLIENT_SECRET": "your_client_secret"
}
}
}
}
The extension will manage the server lifecycle automatically.
Claude Desktop
Add to your Claude Desktop config file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"fanvue": {
"command": "uvx",
"args": ["fanvue-mcp"],
"env": {
"FANVUE_CLIENT_ID": "your_client_id",
"FANVUE_CLIENT_SECRET": "your_client_secret"
}
}
}
}
Restart Claude Desktop after saving the configuration.
Environment Variables
FANVUE_CLIENT_ID: Your Fanvue OAuth Client ID (Required)FANVUE_CLIENT_SECRET: Your Fanvue OAuth Client Secret (Required)MCP_SERVER_PORT: Port to run the server on (Default: 8080)MCP_SERVER_HOST: Host to bind to (Default: 0.0.0.0)MCP_SERVER_URL: Public URL of the server (Default: http://localhost:8080) - used for OAuth redirectsFANVUE_API_URL: Fanvue API URL (Default: https://api.fanvue.com)FANVUE_AUTH_URL: Fanvue Auth URL (Default: https://auth.fanvue.com)DEBUG: Enable debug logging (Default: false)
Development
To develop locally:
- Clone the repository
- Install dependencies:
uv sync - Run the server:
uv run fanvue-mcp
Metadata
Release files for fanvue-mcp 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| fanvue_mcp-0.1.1.tar.gz | 3.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fanvue_mcp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.7 kB
Release files / fanvue_mcp-0.1.1.tar.gz
| Download URL | fanvue_mcp-0.1.1.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3aa5f28bcea32d8c64e8efb894f942f023b25b8ebd180cb25f1e13015f5a6fc0
|
|
BLAKE2b-256 checksum How to use checksums |
48bbc4dd5f0ad1ac0ce9756714604960e5b68468fd129fc1e56a08400ba4090e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.15
|
Release files / fanvue_mcp-0.1.1-py3-none-any.whl
| Download URL | fanvue_mcp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 4.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1e5fa6fd3ad05d87e0fdf75cd28d3bb17c6e0f2250b5dde595bd66ec81ee9dba
|
|
BLAKE2b-256 checksum How to use checksums |
e330cefc06014a6a634b5d908cfa4ff14924d0bbe76db25b92406188bc72599d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.15
|
Security for fanvue-mcp 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.