« Back to Product

Documentation

Send feedback!

MCP Server

The personal area on symcon.de provides an MCP server (Model Context Protocol). It lets AI assistants such as Claude, Cursor or other MCP-capable clients act on the Symcon account on behalf of the user: view and manage licenses, publish modules in the Module Store and invite testers, and with reviewer permissions also handle reviews. The access is authorized with a personal access token that can be revoked at any time.

Warning

The MCP server of the personal area is independent of the Symcon installation. The MCP server of an installation, through which an AI assistant accesses the objects and functions of the system, is configured in the management console under Core Instances → MCP.

Setting up the access

  1. In the settings of the personal area, click "Generate token" under "MCP access". The token is shown exactly once, Symcon stores only its hash. Copy the token and keep it in a safe place.
  2. Register the MCP server in the client. The server is available at https://api.symcon.de/mcp (streamable HTTP), the token is sent in the header Authorization: Bearer <token>.

Claude Code: one command in the terminal.

claude mcp add --transport http symcon https://api.symcon.de/mcp --header "Authorization: Bearer <token>"

Claude Desktop, Cursor and other clients: entry in the MCP configuration.

{
  "mcpServers": {
    "symcon": {
      "type": "http",
      "url": "https://api.symcon.de/mcp",
      "headers": {
        "Authorization": "Bearer <token>"
      }
    }
  }
}

When connecting, the server sends the client instructions on the publishing workflow and the guidelines of the Module Store. This way the assistant can check a module against the review guidelines before submitting it.

Functions

The tools act for the account that generated the token. With the account parameter, accounts that granted this account access via account sharing can be managed as well.

Area Tools Description
Account account_permissions, account_managed_accounts, account_accessing_logins, account_subscription_months, account_redeem_subscription_months View the permissions of the account, account sharing in both directions and the available subscription months, redeem months onto a license.
Licenses licenses_list, licenses_add_license, licenses_remove_license, licenses_send_license_file List licenses with validity and limits, bind a license to the account with its license file or unbind it again, have the license file mailed again.
Module Store store_categories, store_search_modules, store_module, store_previews, store_download_url Read the Module Store: categories, modules with filters and sorting, details of a module per channel, the lists of the start page and download URLs of releases.
Developer area publish_my_modules, publish_module, publish_add_module, publish_set_git, publish_set_localization, publish_delete_localization, publish_set_categories, publish_set_release_flags, publish_submit_release, publish_copy_release_to_channel, publish_end_channel, publish_delete_release, publish_transfer_module Own modules with channel status and download statistics, prepare a new version (repository and commit, texts per language, categories, options), submit it, copy it to another channel, end a channel, discard a template or withdraw a submission, transfer a module to another account.
Testers publish_invite_tester, publish_revoke_test_invitation, publish_remove_tester, publish_redeem_testing_code Invite testers to the testing channel by e-mail, account or invitation code, revoke invitations, remove testers, redeem an invitation code yourself.
Review publish_review_queue, publish_set_review_status, store_review_releases, store_review_download_url Reviewer permissions only: compare submitted releases with the previous version, download them and release or decline them with a remark.

Examples of tasks for the assistant:

  • "Show my licenses and when the subscriptions expire."
  • "Prepare a new beta version of de.mycompany.weather from commit 1a2b3c… and take the release notes from the CHANGELOG."
  • "Check the module against the Module Store guidelines before I submit it."

Notes

  • Several tools change data or send e-mails, for example submitting on stable, inviting testers and deciding a review. It is advisable to ask the assistant to confirm such steps first.
  • Licenses and subscription months cannot be bought via MCP.
  • The access ends with "Revoke token" in the settings. "Generate new token" replaces the current token. A changed or revoked token can stay valid for up to 5 minutes.
Any questions?