Agentify

Agentify runs locally from a Node.js package published to the npm registry: agentify-openapi version 0.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y agentify-openapi@0.1.1. It reads these environment variables: AGENTIFY_BEARER_TOKEN (secret), AGENTIFY_API_KEY (secret), AGENTIFY_API_KEY_HEADER, AGENTIFY_API_KEY_QUERY, AGENTIFY_BASIC_USER and AGENTIFY_BASIC_PASS (secret); set them in the client's configuration for this server. Required arguments: openapi_spec_url.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "agentify": {
      "command": "npx",
      "args": [
        "-y",
        "agentify-openapi@0.1.1"
      ],
      "env": {
        "AGENTIFY_BEARER_TOKEN": "<secret>",
        "AGENTIFY_API_KEY": "<secret>",
        "AGENTIFY_API_KEY_HEADER": "<value>",
        "AGENTIFY_API_KEY_QUERY": "<value>",
        "AGENTIFY_BASIC_USER": "<value>",
        "AGENTIFY_BASIC_PASS": "<secret>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect