Inklusport MCP Server (Python)
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Inklusport MCP Server (Python)
MCP (Model Context Protocol) server with the same foundation as the class example
(mcp>=2.0.0, MCPServer, @server.tool, HTTP transport).
Domain tools do not touch databases: they make HTTP GET requests to
ink-ms-users (port 3002) and ink-ms-sports (port 3003). A per-role agent
(user, coach, organizer, admin) only sees the tools corresponding to their role.
Tools (read & management → microservices)
Tool | Microservice | Endpoint | Test cases |
| sports |
| CP1-HU16.2 |
| sports |
| CP2-HU16.2 |
| sports |
| CP1-HU16.1, CP2-HU16.1 |
| sports |
| CP1-HU16.3, CP2-HU16.3 |
| sports |
| CP1-HU16.4, CP2-HU16.4 |
| sports |
| CP1-HU16.4 |
| sports |
| CP1-HU17, CP2-HU17 |
| sports |
| CP1-HU18 |
| sports |
| CP2-HU18, CP1-HU18.1, CP2-HU18.1 |
| sports |
| CP1-HU18.2 |
| sports |
| CP2-HU18.2 |
| sports |
| CP1-HU18.3, CP2-HU18.3 |
| sports |
| CP1-HU18.4, CP2-HU18.4 |
| sports |
| CP1-HU18.5, CP2-HU18.5 |
| sports |
| CP1-HU19, CP2-HU19 |
| users |
| — |
| sports |
| — |
| users |
| — |
| sports |
| — |
| sports |
| — |
| sports |
| — |
Related MCP server: Enterprise MCP Gateway and Tool Registry
Agents by role
AGENT_ROLE in .env (or at startup) filters the tools:
Role | Tools |
| events, available events, calendar, register, sports, profile, registrations, adaptations |
| events, calendar, profile, routines, adaptations, disabilities (CRUD/activate) |
| events (CRUD/cancel), calendar, disabilities, registrations, adaptations |
| all event management, disabilities, users, routines and adaptations |
| all of the above |
Instructions for Antigravity: agents/usuario.md, entrenador.md, organizador.md, admin.md.
Structure
ink-mcp-inklusport/
├── requirements.txt
├── .env / .env.example
├── README.md
├── agents/ # prompts y config MCP para Antigravity
└── src/
├── server.py # servidor MCP y registro de tools
├── ms_client.py # GET HTTP a Users/Sports
└── client_test.py # cliente de prueba (como en clase)Configuration (.env)
TRANSPORT=streamable-http
HOST=127.0.0.1
PORT=8000
AGENT_ROLE=all
USERS_SERVICE_URL=http://localhost:3002
SPORTS_SERVICE_URL=http://localhost:3003TRANSPORT: sse, streamable-http or stdio.
Quick start (Windows)
1. Environment and installation
cd ink-mcp-inklusport
python -m venv .venv
.\.venv\Scripts\Activate.ps1
pip install -r requirements.txt2. MCP server
Users and Sports are not required to start. Without them, tools
return success=false (microservice unreachable).
python src/server.pyYou should see http://127.0.0.1:8000. Health: http://127.0.0.1:8000/.
3. Test client (another terminal)
.\.venv\Scripts\Activate.ps1
python src/client_test.py4. One process per role (optional)
# terminal 1
$env:AGENT_ROLE="usuario"; $env:PORT="8000"; python src/server.py
# terminal 2
$env:AGENT_ROLE="entrenador"; $env:PORT="8001"; python src/server.py
# terminal 3
$env:AGENT_ROLE="organizador"; $env:PORT="8002"; python src/server.py
# terminal 4
$env:AGENT_ROLE="admin"; $env:PORT="8003"; python src/server.pyConfigure Antigravity with all four: agents/antigravity.roles.mcp.json.
With a single server (AGENT_ROLE=all): agents/antigravity.mcp.json.
Antigravity
Install Antigravity IDE (not the "pure" agent 2.0).
Start the server with
TRANSPORT=streamable-http.Add the MCP:
http://127.0.0.1:8000/mcp.Paste the prompt from
agents/<role>.mdas the agent instructions.Test: "What events are there in Inklusport?". If the response includes the
"via": "mcp"field, the agent is using the server and not making up data.
Microservices
From the monorepo root:
docker compose up -d users-service sports-servicePorts: Users 3002, Sports 3003. Read queries are permitAll.
Write tools (create/edit/cancel/register) call the same
Sports API endpoints and may require a JWT depending on the security profile.
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Strava MCP tools for AI: athletes, activities, segments, clubs, routes. Powered by HAPI MCP server.
Hosted MCP endpoint with realistic fake data for prototyping agents. 12 tools, no setup.
214 tools for AI agents over one MCP endpoint: image, video, audio, 3D, data, storage, mail, GPUs.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables management of Expokossodo 2025 events through 7 MCP tools for checking events, attendee registration, capacity monitoring, attendance confirmation, and real-time statistics. Features JWT authentication with role-based permissions for event coordinators and staff.-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to discover and execute tools via a secure MCP server with JWT authentication, RBAC, rate limiting, and audit logging.1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for eventos event management platform, enabling AI assistants to manage events and tickets via API integration. Supports authentication, ticket CRUD operations, and listing with pagination.1MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that wraps wger fitness/nutrition management platform, providing 15 tools for exercise search, ingredient nutrition lookup, weight tracking, and more, accessible to any MCP-compatible AI agent.-