Placetel Web API

Ein MCP Server mit allen Funktionen der Placetel Web API

MCP (Model Context Protocol) server exposing thecomplete Placetel Web API v2— all124 endpointsas individual, well-annotated tools. Built with the MCP TypeScript SDK (registerTool), Zod validation, and a shared axios client with automatic rate-limit (HTTP 429 /Retry-After) handling.

- Base URL:https://api.placetel.de/v2
- Auth:Bearer token viaPLACETEL_API_KEY
- Transport:stdio (local server for Claude Desktop / Claude Code)

Tools are namedplacetel_<verb>_<resource>(snake_case). Read-only tools carryreadOnlyHint, deletes carrydestructiveHint. Full table with methods, paths and annotations:docs/BUILD-PLAN.md.

npm install cp .env.example .env # then put your Placetel API key into .env npm run build

Get your key athttps://web.placetel.de/integrations/web_api.Never commit.env— it is gitignored.

npm start # runs dist/index.js over stdio npm run smoke # starts the server, lists tools, prints TOOL_COUNT

{ "mcpServers": { "placetel": { "command": "npx", "args": ["-y", "placetel-web-api-mcp-server"], "env": { "PLACETEL_API_KEY": "your_api_key_here" } } } }

Theenvvalue may reference an existing OS environment variable, e.g."PLACETEL_API_KEY": "${MY_PLACETEL_KEY}".

Alternatively point at a local build with"command": "node"and"args": ["<absolute-path>/dist/index.js"].

npm run dev # tsx watch on src/index.ts npm run build # tsc -> dist/

- src/index.ts— entry point, registers all tool modules, connects stdio.
- src/services/— shared client, error mapping, pagination, formatting.
- src/tools/— one module per API domain (contacts.tsis the hand-written reference; the rest are generated to the same pattern from the Swagger spec).
- evaluation.xml— 10 read-only QA pairs (mcp-builder Phase 4).

- CTI, Webex, Microsoft Teams and SIM-card tools require the corresponding Placetel add-on products / real devices; they are implemented and type-checked but may not be exercisable on every account.
- Error messages are actionable (401 → check key, 404 → check id, 422 → validation detail, 429 → rate limited).

Publishing to npm is automated via GitHub Actions (.github/workflows/publish.yml) and runs when aGitHub Release is published:
- Bump the version and updateCHANGELOG.md:npm version patch|minor|major
- Push the tag:git push --follow-tags
- Publish a GitHub Release for that tag:gh release create vX.Y.Z --generate-notes

The workflow then builds and runsnpm publish --provenance. It requires the repository secretNPM_TOKEN— an npmAutomationtoken (Access Tokens → Classic → Automation), which bypasses 2FA. A plain repo push doesnotrepublish npm; only a new release with a bumped version does.

Navigate your Aiven projects and interact with the PostgreSQL®, Apache Kafka®, ClickHouse® and OpenSearch® services

Yunxiao MCP Server provides AI assistants with the ability to interact with the Yunxiao platform.

Get prescriptive CDK advice, explain CDK Nag rules, check suppressions, generate Bedrock Agent schemas, and discover AWS Solutions Constructs patterns.

This AWS Labs Model Context Protocol (MCP) server for CloudTrail enables your AI agents to query AWS account activity for security investigations, compliance auditing, and operational troubleshooting.

Core AWS MCP server providing prompt understanding and server management capabilities.

Analyze CDK projects to identify AWS services used and get pricing information from AWS pricing webpages and API.

Query and analyze your Axiom logs, traces, and all other event data in natural language

Manage and interact with Microsoft Azure services.

Bastion: External Attack Surface Monitoring

Ask your AI assistant about your attack surface: run scans, catch expiring certificates and domains, triage findings, and generate reports.

Agent-ready global image CDN that AI agents can install and operate through MCP.