4d-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FOURD_BASE | Yes | The base URL of your 4D server (e.g., https://your-4d-server.com:443) | |
| FOURD_USER | No | Your 4D username | |
| FOURD_PASSWORD | No | Your 4D password | |
| FOURD_SESSION_MINUTES | No | Session duration in minutes (default: 60) | 60 |
| FOURD_ALLOW_SELF_SIGNED | No | Allow self-signed certificates for development (default: false) | false |
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 |
|---|---|
| loginB | Authenticate with 4D REST server and establish session |
| catalogB | Get 4D database schema information |
| queryC | Query data from a 4D dataclass |
| upsertB | Create or update records in a 4D dataclass |
| deleteB | Delete records from a 4D dataclass |
| callFunctionB | Call an ORDA class function on the 4D server |
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 6 tools
Each tool serves a clear, distinct purpose: authentication, schema introspection, querying, creating/updating, deleting, and calling server functions. There is no meaningful overlap between these operations, so an agent can easily select the right tool for the task.
Most tools use simple lowercase verb names (login, query, upsert, delete), and 'catalog' is a noun but still unambiguous. 'callFunction' breaks the pattern slightly with camelCase, but the naming is otherwise consistent and readable.
With 6 tools, the server is well-scoped for a 4D database interface. Each tool covers a core capability without unnecessary bloat, making the set easy to navigate.
The tool set covers authentication, schema discovery, read, create/update, delete, and server-side function execution. This is a complete lifecycle for typical database operations, with no obvious gaps that would hinder agent workflows.