MCP.so
Sign In

MCP Server - Archi Track

@leandro-jm

Basic information

Category

Other

Transports

stdio

Author

leandro-jm

About MCP Server - Archi Track

MCP Server para pesquisar em um API externa de uma aplicação web

MCP Server - Archi Track config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-tool-archi-track": {
      "command": "node",
      "args": [
        "index.js"
      ]
    }
  }
}

MCP Server - Archi Track tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCP Server - Archi Track?

MCP Server - Archi Track is a server based on the Model Context Protocol (MCP) that provides an API to query information about registered applications. It is configured to run via Cloud Desktop and n8n, and can be built for production.

How to use MCP Server - Archi Track?

Install dependencies with npm install, then start the server with npm start. To run via n8n, create a workflow with a Webhook Node and an Execute Command Node using node /path/to/project/index.js. For Docker, build the image with docker build -t archi-track . and run with docker run --env-file .env -p 3000:3000 archi-track. Production builds require npm run build to generate a build/ folder.

Key features of MCP Server - Archi Track

  • MCP-based API for querying registered application information
  • Runs locally, in Cloud Desktop, or via n8n
  • Supports Docker container deployment
  • Configurable through .env environment variables
  • Production build available (including TypeScript compilation)

Use cases of MCP Server - Archi Track

  • Query application information within an n8n workflow
  • Deploy a containerized API server for registered app data
  • Use locally or on Cloud Desktop for development and testing

Frequently asked questions

1

What are the runtime requirements for MCP Server - Archi Track?

Node.js v18+ and npm or yarn are required. Docker is optional for containerized deployment.

2

How do I configure MCP Server - Archi Track?

Create a `.env` file in the project root with variables: `NWS_API_BASE`, `USER_AGENT`, `TOKEN`, `SERVER_NAME`, and `SERVER_VERSION`.

3

Can I run MCP Server - Archi Track in a Docker container?

Yes. Build the image with `docker build -t archi-track .` and run it with `docker run --env-file .env -p 3000:3000 archi-track`.

4

How do I build MCP Server - Archi Track for production?

Run `npm run build` to compile TypeScript (if used) into a `build/` folder, then run `node build/index.js`. Optionally copy the `.env` file into `build/`.

5

What transport or authentication does MCP Server - Archi Track use?

The README does not specify the transport or authentication method beyond requiring a `TOKEN` in the `.env` file.

Comments

More Other MCP servers