Istedlal MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_HOST | No | Host address for the HTTP server (e.g., 0.0.0.0). | 0.0.0.0 |
| HTTP_PORT | No | Port number for the HTTP server (e.g., 8000). | 8000 |
| LOG_LEVEL | No | Logging level for the server application. | INFO |
| DATABASE_URL | No | PostgreSQL connection string for the database (e.g., postgresql://user:password@db-host:5432/dbname). | |
| MCP_TRANSPORT | No | Transport mode for the server, either 'streamable-http' or 'stdio'. | |
| MCP_BEARER_TOKEN | Yes | Required secret token used for Bearer authentication for the /mcp endpoint. | |
| PGVECTOR_ENABLED | No | Flag to enable pgvector for semantic search features. |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_file_metadataC | Fetch metadata for a specific file by ID. Returns file details including filename, mime_type, size, processing_status, and storage info. |
| search_filesC | Search files using metadata filters. Supports filters like filename, mime_type, processing_status, upload date range. |
| semantic_search_filesB | Semantic search over file embeddings. Use natural language to find relevant content across files. |
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 3 tools
Each tool has a clearly distinct purpose: get_file_metadata retrieves specific file details by ID, search_files filters files based on explicit metadata criteria, and semantic_search_files finds files using natural language queries over embeddings. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern with snake_case: get_file_metadata, search_files, and semantic_search_files. The naming is predictable and readable, with no deviations in style or convention across the set.
With only 3 tools, the server feels thin for a file management domain, as it lacks essential operations like upload, delete, or update files. While the tools are well-defined, the count is borderline low for covering typical file lifecycle needs, potentially limiting agent workflows.
The tool set has significant gaps for file management: there are no tools for uploading, deleting, updating, or processing files, which are core operations in this domain. Agents will face dead ends when trying to perform basic file lifecycle tasks, as the surface only supports retrieval and search functions.