example-mcp
by scalably-io
README.md
# Example MCP
Example MCP server from Scalably. Replace this line.
## Install
Claude Code:
```bash
claude mcp add example -- npx -y @scalably-io/example-mcp
```
Codex:
```bash
codex mcp add example -- npx -y @scalably-io/example-mcp
```
Claude Desktop: download `example-mcp.mcpb` from the latest GitHub release and open it.
## Tools (1)
| Tool | What it does |
|---|---|
| `example_echo` | Return the text you pass in. |
## Configuration
| Variable | Required | Purpose |
|---|---|---|
| `EXAMPLE_LOG_LEVEL` | no | INFO (default) or DEBUG |
## Verify
Each release lists the package version, the `.mcpb` sha256 and the production commit it was derived from in CHANGELOG.md. CI runs the tests and a clean install of the packed tarball on every push.
## Privacy Policy
This server runs locally, on your machine, under your own credentials. It collects no personal data, contains no telemetry, stores nothing persistently, and talks only to the vendor API it wraps. No third party, including Scalably, receives your data. Contact: hello@scalably.io. Canonical copy: https://scalably.io/connector-privacy.html
## License
MIT. Copyright Scalably.
TDQS
C2.7/5.0
Scored across 1 tool
Disambiguation5/5
With only a single tool, there is no possibility of confusion or overlap with other tools. The purpose of example_echo is clear and distinct.
Naming Consistency4/5
The single tool name follows a verb_noun pattern (example_echo), which is consistent and readable. However, with only one tool, consistency across a set cannot be fully established.
Tool Count3/5
At one tool, this server is at the borderline of being too thin. While a minimal example server might justify a single tool, it feels sparse compared to typical well-scoped servers.
Completeness1/5
The server is explicitly a placeholder with a single echo tool and no clear domain coverage. It has no CRUD operations, no real workflow support, and would fail any practical task beyond echoing text.
Maintenance
ActivityMaintained
ResponsivenessNo issues