omnifabric-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OMNIFABRIC_HOST | Yes | The hostname of the OmniFabric instance | |
| OMNIFABRIC_PORT | No | The port number for the OmniFabric instance (default 6001) | 6001 |
| OMNIFABRIC_ROLE | Yes | The role for OmniFabric | |
| OMNIFABRIC_USER | Yes | The username for OmniFabric | |
| OMNIFABRIC_ACCOUNT | Yes | The account UUID for OmniFabric | |
| OMNIFABRIC_PASSWORD | Yes | The password for OmniFabric |
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 |
|---|---|
| run_queryA | Run a SQL statement against the OmniFabric database and return the results. Safety is enforced by the DB user's role/grants, not by this tool — use a read-only account unless writes are explicitly needed. |
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 1 tool
Only one tool exists, so there is no possibility of ambiguity between tools.
With a single tool, naming conventions are trivially consistent.
A single SQL query tool is too few for a database server; agents would likely need schema exploration or metadata tools.
The server lacks essential tools for database interaction, such as listing tables or describing schemas, making it severely incomplete.