Serveur MCP Switcher
Commit 8 nov. 2026Expose les feature flags de l'API Switcher aux assistants IA sous forme d'outils MCP pour lister les domaines, les environnements et récupérer les paramètres des flags.
Aussi connu sous switcherapi/switcher-mcp-server
- Étoiles
- 0
- Outils
- 3
- Téléchargements, 30 jours
- —
- Dernière version
- —
- Dernier commit
- 8 nov. 2026
- Licence
- MIT
Qu'est-ce que Switcher MCP ?
Switcher est un serveur MCP. Expose les feature flags de l'API Switcher aux assistants IA sous forme d'outils MCP pour lister les domaines, les environnements et récupérer les paramètres des flags. Il expose 3 outils, comme list_domains, list_environments, get_feature_flag.
Résumé généré à partir du README du projet
À propos du MCP server Switcher
Ce serveur permet aux développeurs utilisant Claude Desktop, VS Code ou GitHub Copilot CLI de gérer les configurations de feature flags via des assistants IA. Il connecte votre client IA à l'API Switcher, vous permettant d'interroger les informations sur les domaines, les listes d'environnements et les paramètres de flags spécifiques sans quitter votre environnement de développement. Le serveur fournit des outils spécialisés comme list_domains, list_environments et get_feature_flag pour récupérer des données en temps réel depuis votre instance Switcher.
La sécurité est gérée via un flux OAuth 2.1 Authorization Code avec PKCE, garantissant qu'aucun client secret n'est stocké ou partagé. Vous pouvez l'exécuter en tant que sous-processus local via le transport stdio ou en tant que service distant via le transport streamable HTTP. Lors d'une exécution locale, le serveur gère l'authentification en ouvrant votre navigateur pour le consentement et en mettant les identifiants en cache dans un fichier local restreint. Notez que pour des raisons de sécurité, ce serveur est conçu pour la récupération d'informations et ne permet pas de modifier l'état des feature flags.
Ce que vous pouvez faire avec
- 1Découvrir les domaines Switcher accessiblesDemandez à votre assistant IA d'identifier tous les domaines que vous possédez ou sur lesquels vous collaborez actuellement dans Switcher.
- 2Lister les environnements d'un domaineDemandez la liste de tous les environnements disponibles associés à un ID de domaine spécifique.
- 3Récupérer les paramètres d'un flag spécifiqueInterrogez la configuration et les paramètres exacts d'un feature flag à l'aide de sa clé et du nom de son environnement.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Outils MCP Switcher 3
Détectés depuis le READMElist_domainslist_environmentsget_feature_flag
| list_domains | — | |
| list_environments | — | |
| get_feature_flag | — |
Configuration
SWITCHER_API_CERT_PATHSWITCHER_API_URL
| Nom | Description | Type |
|---|---|---|
| SWITCHER_API_CERT_PATH | — | |
| SWITCHER_API_URL | — |
Vérifications automatisées
Exécuté le 14 nov. 2026Rapport complet →Pas encore vérifié. Un serveur nécessite un score de 80, aucune faille sérieuse et suffisamment de données pour que nous puissions effectuer les vérifications. Fonctionnement des vérifications · Ce qu'il faut corriger pour gagner des points
- Dépôt source lié et accessibleswitcherapi/switcher-mcp-server is public and reachablegithub.com/switcherapi/switcher-mcp-server ↗Réussi
- Le nom du package correspond au dépôt sourceNon vérifié
- Provenance du build (attestation Sigstore)Non vérifié
- Licence open source (OSI)MITspdx.org/licenses/MIT.html ↗Réussi
- Commit ou version publiée au cours de l'année écouléeLast commit or release 2026-11-08github.com/switcherapi/switcher-mcp-server ↗Réussi
- OpenSSF ScorecardNon vérifié
- Nom du package non proche d'un package populaireNon vérifié
- Aucun avis critique dans le package ou ses dépendancesNon vérifié
- Aucune instruction cachée destinée au modèle3 tool descriptions and the README read; no override phrases, credential paths or hidden charactersRéussi
- Les outils destructifs sont étiquetésNo tool named like delete, drop or execRéussi
- Le point de terminaison distant répond à la poignée de main MCPNon vérifié
README
Voir sur GitHub
About
Switcher MCP Server exposes Switcher API feature flags to MCP-capable AI assistants (Claude Desktop, VS Code, GitHub Copilot CLI, etc.) as a set of MCP tools. It authenticates on behalf of a real Switcher API user/admin using an OAuth 2.1 Authorization Code + PKCE flow with Dynamic Client Registration, so no client secret is ever stored or shared.
Toggling feature flags will not be supported by this MCP Server for security and consistency reasons.
Quick Start
Requirements
- Python 3.15+
- pipenv for dependency management
- A running switcher-api instance with OAuth enabled
- A switcher-management instance for the
browser-based consent screen (
/oauth/consent)
Authentication
How authentication works depends on the transport.
Streamable HTTP transport
The MCP client (VS Code, Claude, etc.) performs the OAuth flow itself, on the user's machine, when it registers/connects to the MCP server.
- The client calls
/mcpwithout a token and receives a401challenge whoseresource_metadatapoints to the server's protected-resource metadata. - The metadata advertises switcher-api as the authorization server. The client discovers its
OAuth metadata and dynamically registers via
POST /oauth/register(public, PKCE-only client). - The client opens the consent page in the user's browser (switcher-management's
/oauth/consent), which happens during MCP registration. - The client exchanges the code for tokens via
POST /oauth/tokenand sends the access token as a bearer token on every MCP request. The server forwards it to switcher-api, which validates it and its scopes.
If the token is rejected (e.g. consent revoked), tool calls fail with an error asking you to
re-authorize the MCP client. Set SWITCHER_MCP_PUBLIC_URL when the server is reachable through a
different URL than http://<host>:<port>.
Stdio transport
The server is a local subprocess of the client, so it runs the authorization flow itself. When a tool call needs a Switcher API token and none is cached (or the cached one can't be refreshed), it runs the browser-based flow before retrying the call — the browser is not opened eagerly on server startup. That flow:
- Discovers switcher-api's OAuth metadata from
GET {SWITCHER_API_URL}/.well-known/oauth-authorization-server. - Dynamically registers itself as an OAuth client via
POST /oauth/register(no client secret — a public, PKCE-only client) and persists the issuedclient_idlocally. - Opens your default browser (the server runs on your machine) to switcher-management's consent screen so you can log in (if needed) and approve access.
- Receives the authorization code on a local loopback callback (
http://127.0.0.1:<port>/callback) and exchanges it for an access/refresh token pair viaPOST /oauth/token.
In stdio mode, credentials (client id, tokens, expiry) are cached at ~/.switcher-mcp/credentials.json
(file permissions restricted to the current user on POSIX systems) and refreshed automatically
using the rotating refresh token. If the refresh token itself expires, the next tool call will
reopen the browser to re-authorize automatically; if you never complete the consent step, the
authorization attempt times out and the tool call fails with an error telling you to retry.
You can revoke access at any time from switcher-management's Settings → Authorized Apps page.
Running the Server
Configure the target switcher-api instance via the SWITCHER_API_URL environment variable or the
--api-url CLI flag (defaults to http://127.0.0.1:3000).
Stdio Transport
For the default stdio transport:
pipenv run python -m switcher_mcp_server.server --api-url https://switcherapi.com/api
Streamable HTTP Transport (embedded uvicorn - single worker)
For a hosted/remote MCP server:
pipenv run python -m switcher_mcp_server.server --transport streamable-http --host 0.0.0.0 --port 8000
The server will be reachable at http://<host>:<port>/mcp.
Streamable HTTP Transport (external uvicorn - multiple workers)
For containerized/production deployments that need custom TLS certificates
or multiple workers, run switcher_mcp_server.asgi:create_app with your own uvicorn process
instead (the --factory flag is required, since the app is built from a factory function):
pipenv run uvicorn switcher_mcp_server.asgi:create_app \
--factory \
--host 0.0.0.0 \
--port 8443 \
--ssl-certfile=/etc/certs/ca.crt \
--ssl-keyfile=/etc/certs/ca.key \
--workers 4
If the target switcher-api instance is also served under that certificate, set
SWITCHER_API_CERT_PATH to the same cert file so outbound requests verify against it instead of
the default CA bundle:
export SWITCHER_API_CERT_PATH=/etc/certs/ca.crt
Configuration
| Variable | CLI flag | Default | Description |
|---|---|---|---|
SWITCHER_API_URL |
--api-url |
http://127.0.0.1:3000 |
Base URL of the target switcher-api instance |
SWITCHER_API_INTERNAL_URL |
--api-internal-url |
unset (uses SWITCHER_API_URL) |
Internal switcher-api URL used only for server-side tool requests |
SWITCHER_API_CERT_PATH |
— | unset | Path to the TLS certificate for Switcher API |
SWITCHER_MCP_TRANSPORT |
--transport |
stdio |
stdio or streamable-http |
SWITCHER_MCP_HOST |
--host |
0.0.0.0 |
Bind host for the streamable HTTP transport |
SWITCHER_MCP_PORT |
--port |
8000 |
Bind port for the streamable HTTP transport |
SWITCHER_MCP_PUBLIC_URL |
--public-url |
http://<host>:<port> |
Externally reachable MCP URL used as the OAuth resource identifier (streamable HTTP only) |
SWITCHER_MCP_CREDENTIALS_PATH |
— | ~/.switcher-mcp/credentials.json |
Override the persisted OAuth credentials cache location |
CLI flags take precedence over environment variables.
Internal API URL (hosted deployments)
SWITCHER_API_URL is the public URL: it is used for OAuth issuer discovery, authorization,
token and refresh requests. Optionally, SWITCHER_API_INTERNAL_URL points MCP server-to-API tool
requests at an internal endpoint (e.g. a Kubernetes service), bypassing the public ingress. The
internal URL is never advertised to OAuth clients. When unset, tool requests use SWITCHER_API_URL.
env:
- name: SWITCHER_API_URL
value: https://switcherapi.com/api
- name: SWITCHER_API_INTERNAL_URL
value: http://switcher-api.switcherapi.svc.cluster.local:3000
MCP Client Configuration
Example stdio configuration for an MCP client (e.g. Claude Desktop, VS Code):
{
"mcpServers": {
"switcher": {
"command": "pipenv",
"args": ["run", "python", "-m", "switcher_mcp_server.server"],
"cwd": "/path/to/switcher-mcp-server",
"env": {
"SWITCHER_API_URL": "https://switcherapi.com/api"
}
}
}
}
Available Tools
| Tool | Description |
|---|---|
list_domains |
List the domains the authenticated user owns and/or collaborates on. |
list_environments |
List environment names for a given domain id. |
get_feature_flag |
Get a feature flag's settings by key, domain name, and optional environment. |
Available Prompts
Prompts are user-selectable, guided templates (e.g. shown as /switcher_domains in MCP clients)
that drive one of the tools above and ask the model to summarize or analyze its result. All
prompts are prefixed with switcher_ for easy discovery.
| Prompt | Drives | Description |
|---|---|---|
switcher_domains |
list_domains |
Discover and summarize the Switcher domains accessible to the authenticated user. |
switcher_environments |
list_environments |
List a Switcher domain's environments. |
switcher_get_feature |
get_feature_flag |
Fetch a Switcher feature flag's settings. |
Development
Quality Gate
make install # pipenv install --dev
make lint # pylint switcher_mcp_server
make test # pytest with coverage (coverage.xml)
make cover # generate an HTML coverage report (htmlcov/)
make e2e-tools # manual, configurable e2e tool validation (see scripts/e2e/README.md)
make e2e-prompts # manual, configurable e2e prompt validation (see scripts/e2e/README.md)
Both pylint and pytest must pass before merging changes. Tests use pytest-httpx to mock all
outbound HTTP calls to switcher-api — no live server is required to run the test suite.
Contributing
Read our Contributing guide to learn about our development process, and how to propose enhancements and improvements.
AI Disclaimer
This project was designed and implemented with AI-assisted tools. We have thoroughly reviewed and tested all AI-generated contributions to ensure they meet our quality standards and align with our project's goals. We are committed to transparency about our use of AI and will continue to disclose any significant AI contributions in the future.
External contributions from the community are equally valued and will be reviewed with the same standards, regardless of whether they were assisted by AI or not. We encourage all contributors to disclose their use of AI tools in their contributions to maintain transparency and foster trust within our community.
Questions sur Switcher MCP
Quels outils Switcher MCP fournit-il ?
Il expose 3 outils, dont list_domains, list_environments, get_feature_flag.
Puis-je activer ou désactiver des feature flags avec ce serveur ?
Non, la modification des feature flags n'est pas prise en charge pour des raisons de sécurité et de cohérence.
Comment le serveur gère-t-il l'authentification ?
Il utilise un flux OAuth 2.1 Authorization Code + PKCE avec Dynamic Client Registration, garantissant qu'aucun client secret n'est stocké ou partagé.
Où sont stockées les informations d'identification en mode stdio ?
Les identifiants tels que le client ID et les tokens sont mis en cache localement dans ~/.switcher-mcp/credentials.json.