Appmixer MCP Server

How to use

Once you have the Appmixer MCP Server running, you can connect your MCP client (VS Code MCP, Claude Desktop, Cursor, Windsurf, Claude Code, or any compliant client) to issue commands that control Appmixer flows, retrieve flow information, and trigger components. Use the MCP gateway to automatically surface available tools as you build flows. Start flows, fetch logs, and trigger components directly from your chat or automation prompts to compose end‑to‑end workflows.

Key usage patterns include: finding flows by name, starting and stopping flows, and triggering specific components via HTTP calls. You can also emit app events and examine flow logs to monitor behavior. Tools exposed by the Appmixer MCP Server appear in your MCP client’s tool list, and they update dynamically as you start or stop flows that include the MCP Gateway component.

How to install

Prerequisites you need before installing:

• Node.js 20 or newer
• An MCP client such as VS Code MCP, Claude Desktop, Cursor, Windsurf, or Claude Code

Install and configure the Appmixer MCP Server using the following step‑by‑step configuration. This example shows the standard local runtime via npx, with environment variables for Appmixer access.

{
  "mcpServers": {
    "appmixer_mcp": {
      "command": "npx",
      "args": [
        "appmixer-mcp"
      ],
      "env": {
        "APPMIXER_BASE_URL": "<your-appmixer-tenant-api-base-url>",
        "APPMIXER_ACCESS_TOKEN": "<your-appmixer-access-token>",
        "APPMIXER_USERNAME": "<optional-appmixer-username>",
        "APPMIXER_PASSWORD": "<optional-appmixer-password>"
      }
    }
  }
}

Additional steps for common clients

Claude Desktop, Windsurf, VS Code, Cursor, and Claude Code offer streamlined ways to add the Appmixer MCP Server. Use the corresponding client’s MCP setup flow and supply the same command and environment variables shown above. This ensures the Appmixer MCP Server starts in the client environment and is discoverable by your MCP workflows.

Configuration

The Appmixer MCP Server uses environment variables to configure access and behavior. You set these variables in the MCP server configuration for your client. Available variables include the base URL for your Appmixer tenant, the access token, and optional user credentials. You can also enable or disable specific tool groups with the TOOLS variable.

Security and tokens

You can provide the APPMIXER_ACCESS_TOKEN securely to authenticate with Appmixer. A token can expire, so you may prefer using APPMIXER_USERNAME and APPMIXER_PASSWORD for session credentials. If token expiration is a concern, coordinate with your Appmixer admin to understand the system token expiry setting.

Tools

API Tools exposed by the Appmixer MCP Server include operations to manage flows and components, such as getting flows, starting or stopping flows, triggering components, and retrieving logs. There are also App Events and flow log queries to help you observe and control your automation. The MCP Gateway tools surface dynamically based on the flows and components you connect.

{
  "tools": [
    {"name": "get-flows", "description": "List flows with optional name pattern"},
    {"name": "get-flow", "description": "Retrieve a specific flow by ID"},
    {"name": "delete-flow", "description": "Delete a flow by ID"},
    {"name": "start-flow", "description": "Start a flow by ID"},
    {"name": "stop-flow", "description": "Stop a running flow by ID"},
    {"name": "trigger-component", "description": "Send an HTTP trigger to a flow component"},
    {"name": "send-app-event", "description": "Emit an App Event with data"},
    {"name": "get-flow-logs", "description": "Query flow logs by ID with a search query"},
    {"name": "MCP Gateway Tools", "description": "Dynamic tools surfaced via MCP Gateway in flows"}
  ]
}

Troubleshooting

If you don’t see the Appmixer MCP Server in your MCP client, verify that the server process started successfully and that the environment variables are correct. Check that the base URL and access token are valid and that the client is configured to use the same MCP server name you defined (for example, appmixer_mcp). If tokens expire, refresh them and update the configuration accordingly.

get-flows

Patterned flow listing and filtering by name

get-flow

Retrieve a specific flow by ID

delete-flow

Delete a flow by ID

start-flow

Start a flow by ID

stop-flow

Stop a flow by ID

trigger-component

Trigger a flow component via HTTP method with a body payload

send-app-event

Emit a named App Event with data payload

get-flow-logs

Query logs for a flow using Lucene syntax