exact-synergy-globe-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXACT_API_AUTH | No | Authentication method: NTLM, Basic, or pre-issued OAuth credentials. | |
| EXACT_API_KIND | No | Exact installation kind, e.g. 'synergy'. | |
| EXACT_READ_ONLY | No | Whether to run in read-only mode. The server is read-only by default. | true |
| EXACT_API_DOMAIN | No | Domain for NTLM authentication (e.g. EXAMPLE). | |
| EXACT_API_DB_NAME | No | Database name for NTLM authentication (e.g. Synergy). | |
| EXACT_API_BASE_URL | No | Exact REST/OData Entity Services base URL. If not set, the server starts in offline discovery mode. | |
| EXACT_API_PASSWORD | No | Password for authentication. | |
| EXACT_API_USERNAME | No | Username for authentication. | |
| EXACT_API_DB_SERVER | No | Database server for NTLM authentication. | |
| EXACT_ALLOWED_ENTITIES | No | Comma-separated list of allowed entities (e.g. 'Account,Resource,Request'). |
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": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| exact_get_server_infoA | Check configuration, connectivity, product selection, and live metadata availability without exposing connection secrets. |
| exact_get_capabilitiesA | Return capabilities detected or verified against the configured Exact installation. |
| exact_list_entitiesA | List live metadata entities allowed by the effective read policy. |
| exact_get_entity_schemaB | Return keys, properties, types, and discovered support for an allowed entity. |
| exact_get_entityB | Read one allowed entity record by a validated simple or composite key. |
| exact_list_entity_recordsA | Read allowed entity records using structured filters, validated fields, ordering, limits, and a safe continuation cursor. Raw OData is not accepted. |
| exact_list_actionsA | List only public actions discovered in live Exact metadata; internal-looking actions are excluded. |
| exact_get_action_schemaB | Return the discovered schema for a public Exact action. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Exact products | Configured product and metadata source without secrets |
| Exact capabilities | Capabilities detected or verified against Exact |
| Effective Exact policies | Effective read/write policy without connection secrets |
| synergy entities | Allowed synergy entity summaries from live metadata |
| globe entities | Allowed globe entity summaries from live metadata |
TDQS
Scored across 8 tools
Each tool addresses a distinct layer: connection/capabilities, entity and action catalogs, schema discovery, and record reads. The overlap between list_entities and list_entity_records is clarified by 'metadata entities' versus 'entity records', so selection should be unambiguous.
All tools share the 'exact_' prefix and use a consistent verb-noun scheme: get_ for single objects/schemas/info and list_ for catalogs. There is no mix of verb styles or casing.
Eight tools is a well-scoped size for an Exact integration. Each tool covers a distinct need without redundant or trivial additions.
The read-side surface is complete: server health, capabilities, entity/action discovery, schemas, single-record reads, and filtered list reads are all present. The only notable gap is that action schemas can be inspected but there is no execute_action tool to invoke discovered actions, leaving a potential dead end for action workflows.