custom-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JWKS_URI | Yes | JWKS endpoint for signature verification | |
| LOG_LEVEL | No | Log level: debug/info/warn/error (default info) | |
| AWS_REGION | Yes | AWS region, e.g. us-east-1 | |
| JWT_SECRET | No | HS256 fallback secret (optional, dev/local only) | |
| OAUTH_ISSUER | Yes | Expected JWT iss claim | |
| OAUTH_AUDIENCE | Yes | Expected JWT aud claim | |
| S3_BUCKET_NAME | Yes | Default S3 bucket | |
| SLACK_BOT_TOKEN | Yes | Slack bot token (xoxb-...) | |
| AWS_ACCESS_KEY_ID | Yes | AWS access key ID (secret) | |
| DYNAMO_TABLE_NAME | Yes | DynamoDB table with partition key id | |
| RATE_LIMIT_PER_MIN | No | Rate limit per minute (default 100) | |
| RETRY_MAX_ATTEMPTS | No | Maximum retry attempts (default 3) | |
| RETRY_BASE_DELAY_MS | No | Base retry delay in ms (default 200) | |
| AWS_SECRET_ACCESS_KEY | Yes | AWS secret access key (secret) | |
| SLACK_DEFAULT_CHANNEL | Yes | Default Slack channel, e.g. #annotations |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| s3_uploadB | Upload a base64-encoded object to S3. |
| s3_downloadB | Download an object from S3 and return it base64-encoded. |
| dynamo_readA | Read a single record from DynamoDB by primary key 'id'. |
| dynamo_writeC | Write a record to DynamoDB keyed by 'id'. |
| slack_notifyA | Post a message to a Slack channel. |
| annotation_statusA | Read or update an annotation task's status, optionally notifying Slack. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: annotation_status for task status, dynamo_read/write for database, s3_download/upload for storage, slack_notify for messaging. No overlap.
Most tools follow verb_noun pattern (dynamo_read, dynamo_write, s3_download, s3_upload, slack_notify), but 'annotation_status' is an outlier as a noun phrase.
6 tools is well-scoped for a server covering annotation, database, storage, and Slack integration. It feels neither too few nor too many.
Each service has basic operations but lacks deletions, updates, and lists. For annotation only status is provided. This leaves notable gaps for typical workflows, but the server may be intentionally scoped.