Tideways MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level (debug, info, warn, error) | info |
| TIDEWAYS_ORG | Yes | Tideways organization name | |
| TIDEWAYS_TOKEN | Yes | Tideways API access token | |
| TIDEWAYS_PROJECT | Yes | Tideways project name | |
| TIDEWAYS_BASE_URL | No | Tideways API base URL | https://app.tideways.io/apps/api |
| TIDEWAYS_RATE_LIMIT | No | API requests per hour — match to your plan (Team/Pro: 2500, Standard: 1000, Basic: 250) | 2500 |
| TIDEWAYS_MAX_RETRIES | No | Maximum API retry attempts | 3 |
| TIDEWAYS_REQUEST_TIMEOUT | No | API request timeout (ms) | 30000 |
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 |
|---|---|
| get_performance_metricsA | Retrieve aggregate performance metrics and system-wide statistics in JSON format. Use for monitoring overall application health, trends, and high-level performance overview (use get_traces for detailed individual request analysis). |
| get_performance_summaryB | Retrieve time-series performance summary data in 15-minute intervals in JSON format for trend analysis and historical comparison. Returns data aggregated in 15-minute time buckets showing requests, errors, and 95th percentile response times. |
| get_issuesA | Retrieve and analyze recent errors, exceptions, and performance issues in JSON format for actionable insights |
| get_historical_dataA | Retrieve historical performance data in JSON format for a specific date with configurable granularity. Analyze daily, weekly, or monthly performance trends, transaction reports, and time-series metrics. |
| get_tracesA | Analyze individual trace samples in JSON format for detailed bottleneck identification and performance debugging. Use for investigating specific slow requests, not system-wide statistics (use get_performance_metrics for aggregate data). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/5hahiL/tideways-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server