outlty-mcp
A Python MCP server exposing your FastAPI API-key routes as MCP tools for use in Claude Code (and any MCP client).
Tools
- list_user_apis
- get_user_api
- create_user_api
- make_request
Prerequisites
- Python 3.10+
- Your backend running and accessible (default base URL: http://localhost:8000)
- An API key valid for the backend. The backend supports either:
X-API-Key: <key>Authorization: ApiKey <key>
Install
python -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
Run with uvx (recommended)
You can run this server without a local install using uv.
Local checkout:
uvx --from . outlty-mcp
From Git repository (example):
uvx --from git+https://github.com/your-org/outly-mcp-server.git outlty-mcp
You can also pin a version published to an index:
uvx outlty-mcp
Run (standalone debug)
This server communicates via stdio when launched by an MCP client, but you can validate it imports:
python server.py
Configuration (env)
OUTLY_MCP_API_BASE_URL(default:http://localhost:8000)OUTLY_MCP_API_KEY(required)OUTLY_MCP_AUTH_HEADER(default:X-API-Key; set toAuthorizationto sendAuthorization: ApiKey <key>)
Claude Code configuration (JSON)
Add this to your Claude configuration (e.g., ~/.config/anthropic/claude_desktop_config.json or the workspace .claued.json depending on your setup). See Claude docs for exact location.
{
"mcpServers": {
"outlty-mcp": {
"command": "uvx",
"args": ["outlty-mcp"],
"env": {
"OUTLY_MCP_API_BASE_URL": "http://localhost:8000",
"OUTLY_MCP_API_KEY": "ak_xxx_your_secret",
"OUTLY_MCP_AUTH_HEADER": "X-API-Key"
}
}
}
}
If you prefer Authorization header:
{
"mcpServers": {
"outlty-mcp": {
"command": "uvx",
"args": ["outlty-mcp"],
"env": {
"OUTLY_MCP_API_BASE_URL": "http://localhost:8000",
"OUTLY_MCP_API_KEY": "ak_xxx_your_secret",
"OUTLY_MCP_AUTH_HEADER": "Authorization"
}
}
}
}
Tool schemas
- list_user_apis: GET
/api-key/user-apis - get_user_api(id: string): GET
/api-key/user-apis/{id} - create_user_api(user_query: string): POST
/api-key/user-apis - make_request(url: string, input_data: object): POST
/api-key/user-apis/make-request
Metadata
Release files for outlty-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 | |
|---|---|---|---|---|
| outlty_mcp-0.1.1.tar.gz | 4.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| outlty_mcp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.9 kB
Release files / outlty_mcp-0.1.1.tar.gz
| Download URL | outlty_mcp-0.1.1.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d1acf1b231ba1d1b2d0a4bd26b5f835f5677be9dfb437022ee89c018753f3126
|
|
BLAKE2b-256 checksum How to use checksums |
e9c845f8b50067b350d0f54024a9a6ba275c1f1686e3fb268f9fea9ab1a2dd48
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.9
|
Release files / outlty_mcp-0.1.1-py3-none-any.whl
| Download URL | outlty_mcp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 4.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1853987662e4588246a7486109e56c041d97baf0077085d3fe0a63b7961a39a9
|
|
BLAKE2b-256 checksum How to use checksums |
d80bb98acfb92e76f99acd1a900d63507151006484606bcddabdb3d9c2eb249b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.9
|
Security for outlty-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.