AIMCP
AIMCP is an MCP (Model Context Protocol) server that enables teams to distribute MCP tool specifications from GitLab repositories to IDEs like Cursor and VS Code. The server discovers tools.json files in repositories, dynamically generates MCP tools from their specifications, and serves referenced files as resources through a secure URI scheme.
Features
- GitLab Integration: Automatically discovers and fetches
tools.jsonfiles from configured repositories - Dynamic Tool Generation: Creates MCP tools from specifications at runtime
- Secure Resource Access: Serves repository files via
aimcp://URI scheme with access control - Dual Caching: Caches both tool specifications and file content for optimal performance
- Conflict Resolution: Handles duplicate tool names across repositories with configurable strategies
- Async Architecture: Built on
fastmcpfor high-performance async operations
Installation
pip install aimcp
Quick Start
- Create a configuration file
config.yaml:
gitlab:
base_url: "https://gitlab.example.com"
token: "your-gitlab-token"
repositories:
- path: "team/tools-repo"
branch: "main"
cache:
type: "memory"
ttl: 3600
conflict_resolution: "prefix"
- Run the server:
aimcp
- Connect your IDE to the MCP server at the configured endpoint.
Tool Specifications
Each repository must contain a tools.json file following the MCP specification. Example:
{
"tools": [
{
"name": "analyze_code",
"description": "Analyze code quality and suggest improvements",
"resourceRefs": ["analyzer_script", "analyzer_rules"]
}
}
],
"resources": [
{
"name": "analyzer_script",
"uri": "scripts/analyze.py",
},
{
"name": "analyzer_rules",
"uri": "configs/rules.yaml"
}
]
}
Configuration
Conflict Resolution Strategies
prefix: Add repository prefix to tool names (repo1_toolname,repo2_toolname)priority: First repository in configuration order winserror: Fail startup with detailed conflict reportmerge: Combine tool descriptions and resource lists
Cache Options
memory: In-memory caching (default)redis: Redis-backed caching for distributed setups (not implemented)
Development
Prerequisites
- Python 3.13+
- uv (recommended package manager)
Setup
# Clone the repository
git clone https://github.com/yourusername/aimcp.git
cd aimcp
# Install dependencies
uv sync --dev
# Run tests
uv run pytest
# Run linting
uv run ruff check .
# Run type checking
uv run mypy .
License
This project is licensed under the MIT License - see the LICENSE file for details.
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Vibe coding product
Generated with Claude
Metadata
Release files for airulermcp 0.3.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 | |
|---|---|---|---|
| airulermcp-0.3.1.tar.gz | 67.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| airulermcp-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 102.4 kB
Release files / airulermcp-0.3.1.tar.gz
| Download URL | airulermcp-0.3.1.tar.gz |
|---|---|
| Size | 67.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
acb82ad6db2fcd01d3f9f7f11cc9e5f70f57310a9774978df299d7d52340ee5a
|
|
BLAKE2b-256 checksum How to use checksums |
a326422a4ca180c65615650afd2129213927d4dc8daf81c6fadf18e0a2908d25
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 5, 2025.
Transparency logRelease files / airulermcp-0.3.1-py3-none-any.whl
| Download URL | airulermcp-0.3.1-py3-none-any.whl |
|---|---|
| Size | 34.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4a5e648fc1e1b310e7f40572b442ccba3757331e1e24d9fc5d4b6da3da658d51
|
|
BLAKE2b-256 checksum How to use checksums |
a1bd350a59c27941cab516ca9396d6db30e14ceb248bd815782a9386cb855f97
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 5, 2025.
Transparency log