1 MCP server, 13 databases, zero config. Multi-protocol transport with Auth + RBAC.
Connect Mosta to Claude, Cursor or any other MCP client and it stops being a tab you switch to. 1 MCP server, 13 databases, zero config. Multi-protocol transport with Auth + RBAC. The mosta mcp server is what makes that connection.
Octonet (@mostajs/net) is a Node.js multi-transport server that exposes a single @mostajs/orm schema as 11 different network protocols simultaneously : REST, GraphQL, WebSocket, SSE, JSON-RPC, MCP, gRPC, tRPC, OData, NATS, Arrow Flight.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Endpoint — MéthodeSanitizer — Les champs password, hash, verifyToken, resetToken, apiKeyHash, secret, privateKey sont automatiquement strippés de toutes les réponses JSON parTest — The Test tool exposed by this serverServer — The Server tool exposed by this serverPublic — The Public tool exposed by this serverObservability — The Observability tool exposed by this serverBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: MOSTAJS_NET_URL, MOSTAJS_NET_API_KEY, SCHEMAS_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Mosta's toolset — Endpoint, Sanitizer, Test and 3 more — is a fair guide to whether it matches your workflow. It is maintained by apolocine; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Endpoint | Méthode |
| Sanitizer | Les champs password, hash, verifyToken, resetToken, apiKeyHash, secret, privateKey sont **automatiquement strippés** de toutes les réponses JSON par un middleware global. Aucun risque de leak à travers /api/v1/User?limit |
| Test | The Test tool exposed by this server. |
| Server | The Server tool exposed by this server. |
| Public | The Public tool exposed by this server. |
| Observability | The Observability tool exposed by this server. |
{
"mcpServers": {
"mosta-net": {
"command": "npx",
"args": ["-y", "@mostajs/net"],
"env": {
"MOSTAJS_NET_URL": "your-value",
"MOSTAJS_NET_API_KEY": "your-value",
"SCHEMAS_PATH": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| MOSTAJS_NET_URL | Endpoint or connection string the server talks to. | Yes |
| MOSTAJS_NET_API_KEY | Credential the server authenticates with. | Yes |
| SCHEMAS_PATH | Filesystem location the server is allowed to use. | Optional |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.