Frontier Intelligence
by ilyasni
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | MCP server port | 8100 |
| EMBED_DIM | No | Embedding dimension | 2560 |
| S3_REGION | No | S3 region | ru-central-1 |
| TG_SOCKS5 | No | Telegram SOCKS5 proxy configuration in format HOST:PORT:USER:PASS | |
| ADMIN_PORT | No | Admin UI port | 8101 |
| POSTGRES_DB | No | PostgreSQL database name | frontier |
| SEARXNG_URL | No | SearXNG server URL | http://searxng:8080 |
| TG_API_ID_0 | Yes | Telegram API ID for account 0 | |
| TG_API_ID_1 | No | Telegram API ID for account 1 | |
| MTPROXY_HOST | No | MTProxy host | |
| MTPROXY_PORT | No | MTProxy port | 443 |
| TG_PROXY_DSN | No | Telegram proxy DSN | |
| PADDLEOCR_URL | No | PaddleOCR service URL | http://paddleocr:8008 |
| POSTGRES_USER | No | PostgreSQL username | frontier |
| TG_API_HASH_0 | Yes | Telegram API hash for account 0 | |
| TG_API_HASH_1 | No | Telegram API hash for account 1 | |
| TG_PROXY_HOST | No | Telegram proxy host | |
| TG_PROXY_PASS | No | Telegram proxy password | |
| TG_PROXY_PORT | No | Telegram proxy port | |
| TG_PROXY_USER | No | Telegram proxy username | |
| WG_SOCKS_HOST | No | WireGuard SOCKS host | |
| WG_SOCKS_PORT | No | WireGuard SOCKS port | |
| GIGACHAT_MODEL | No | GigaChat model for general use | GigaChat-2 |
| GIGACHAT_SCOPE | No | GigaChat API scope | GIGACHAT_API_PERS |
| MTPROXY_SECRET | No | MTProxy secret | |
| NEO4J_PASSWORD | Yes | Neo4j password | |
| S3_BUCKET_NAME | Yes | S3 bucket name | |
| S3_ENDPOINT_URL | No | S3 endpoint URL | https://s3.cloud.ru |
| GRAFANA_PASSWORD | Yes | Grafana password | |
| S3_ACCESS_KEY_ID | Yes | S3 access key ID | |
| TG_REQUIRE_PROXY | No | Require proxy for Telegram (1 to enable) | 1 |
| GIGACHAT_BASE_URL | No | GigaChat API base URL | https://gigachat.devices.sberbank.ru/api/v1 |
| POSTGRES_PASSWORD | Yes | PostgreSQL password | |
| GIGACHAT_MODEL_PRO | No | GigaChat Pro model | GigaChat-2-Pro |
| GIGACHAT_CREDENTIALS | Yes | GigaChat API credentials | |
| S3_SECRET_ACCESS_KEY | Yes | S3 secret access key | |
| GIGACHAT_VISION_MODEL | No | GigaChat Vision model | GigaChat-2-Pro |
| INDEXING_MAX_CONCURRENCY | No | Maximum concurrency for indexing | 1 |
| GIGACHAT_EMBEDDINGS_MODEL | No | GigaChat embeddings model | EmbeddingsGigaR |
| GIGACHAT_VERIFY_SSL_CERTS | No | Verify SSL certificates for GigaChat API | False |
| GIGACHAT_MIN_REQUEST_INTERVAL_MS | No | Minimum request interval for GigaChat API in milliseconds | 5000 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
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/ilyasni/frontier-intelligence'
If you have feedback or need assistance with the MCP directory API, please join our Discord server