Skip to main content
Glama

@terros-inc/mcp

Production-ready MCP server scaffold for the Terros platform. This initial version implements User API tools.

Implemented tools

  • terros_get_current_user - Get the authenticated user profile (GET /users/me)

  • terros_list_users - List users with optional role, limit, and offset

  • terros_get_user - Get a user by ID

Requirements

  • Node.js 20+

  • npm

  • Terros API key

Setup

pnpm install
cp .env.example .env
pnpm build
pnpm start

Environment variables

Variable

Required

Default

Description

TERROS_API_KEY

Yes

-

API key sent as Authorization: Bearer <key>

TERROS_API_BASE_URL

No

https://api.terros.com/v1

Base URL for Terros API

MCP client configuration

Claude Desktop

Add this to Claude Desktop MCP config:

{
  "mcpServers": {
    "terros": {
      "command": "node",
      "args": ["/absolute/path/to/terros-mcp/dist/index.js"],
      "env": {
        "TERROS_API_KEY": "<your_key>",
        "TERROS_API_BASE_URL": "https://api.terros.com/v1"
      }
    }
  }
}

Cursor

Configure MCP server entry:

{
  "name": "terros",
  "command": "node",
  "args": ["/absolute/path/to/terros-mcp/dist/index.js"],
  "env": {
    "TERROS_API_KEY": "<your_key>",
    "TERROS_API_BASE_URL": "https://api.terros.com/v1"
  }
}

OpenClaw

Example server launch:

TERROS_API_KEY=<your_key> TERROS_API_BASE_URL=https://api.terros.com/v1 node dist/index.js

Development

pnpm dev

Build

pnpm build

Available Tools

6 tools
terros_get_companyA

Get a company from Terros by company ID. Omit companyId to get the current user's company.

Inputs: companyId.

terros_get_current_userB

Get the authenticated user's own profile from Terros.

Inputs: no named parameters.

terros_get_teamB

Get a Terros team by ID, including child teams and members.

Inputs: teamId (required).

terros_get_userB

Get a Terros user by User ID (e.g. U:abc123), email address, or clientUserId.

Inputs: userId (required).

terros_list_teamsC

List teams in the Terros workspace. Filter by company or archived status.

Inputs: companyId, showArchived.

terros_list_usersB

List users in the Terros workspace. Filter by company, team, specific user IDs, or archived status.

Inputs: companyId, teamId, userIds, showArchived.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific resources: get_company, get_current_user, get_team, get_user, list_teams, and list_users. There is no overlap in functionality, as each tool handles a unique entity or action, making it easy for an agent to select the correct one without confusion.

    Naming Consistency5/5

    All tool names follow a consistent 'terros_verb_noun' pattern, using snake_case throughout. The verbs (get, list) are used predictably, with 'get' for retrieving single entities and 'list' for collections, ensuring a uniform and readable naming convention across the toolset.

    Tool Count5/5

    With 6 tools, the server is well-scoped for managing users, teams, and companies in a workspace. Each tool earns its place by covering essential operations without bloat, providing a focused and manageable interface for the domain, which is typical for such administrative functions.

    Completeness3/5

    The toolset covers read operations (get and list) for users, teams, and companies, but lacks create, update, or delete functionalities. This is a notable gap, as agents cannot perform full lifecycle management, though they can work around it by using existing data for queries and reporting.

    Related MCP Connectors