Verodat Context Protocol Gateway

Abstract

This repository delivers a compliant implementation of the Model Context Protocol (MCP) server layer specifically engineered for Verodat. It establishes a robust conduit, enabling advanced AI agents (such as those running in Claude Desktop environments) to interact fluidly with Verodat's powerful data management and manipulation services.

Verodat MCP Bridge

This codebase furnishes the necessary infrastructure for an MCP server that exposes Verodat's data functionalities to autonomous AI systems via standardized tool interfaces.

Core Functionality

The Verodat MCP Bridge offers a formalized mechanism for generative models to query, interpret, and modify data residing within the Verodat ecosystem, adhering strictly to the MCP specification for data ingestion, schema design, and lifecycle administration.

Functional Tiers

The exposed capabilities are segmented into three distinct, additive tiers reflecting increasing levels of data interaction authority:

Tier 1: Information Extraction (8 Functions)

This foundational set focuses exclusively on read operations and context retrieval:

• get-accounts: Enumerates accessible organization accounts.
• get-workspaces: Lists available workspaces under a specified account.
• get-datasets: Retrieves a catalog of datasets within a working area.
• get-dataset-output: Fetches the granular record content of a specific dataset.
• get-dataset-targetfields: Obtains the structural schema definitions for a dataset.
• get-queries: Fetches previously executed or stored AI analysis requests.
• get-ai-context: Retrieves environmental parameters and data structures pertinent to the workspace.
• execute-ai-query: Triggers AI-driven analytical processing against accessible datasets.

Tier 2: Schema Authoring (9 Functions)

Includes all Tier 1 functions, augmented by the ability to initialize new data structures:

• create-dataset: Provisions a novel dataset complete with a defined schema.

Tier 3: Data Administration (10 Functions)

Incorporates all Tier 2 capabilities, adding mutable data operations:

• upload-dataset-rows: Ingests new records into an existing, structured dataset.

Prerequisites for Deployment

• Node.js runtime environment (version 18 or newer is required)
• Git for source control management
• Claude Desktop application (necessary for client-side tool invocation)
• Valid Verodat account credentials and an associated AI service API credential.

Deployment Procedure

Expedited Setup via Smithery

To automate the deployment of the Verodat MCP Bridge for Claude Desktop via the Smithery registry:

npx -y @smithery/cli install @Verodat/verodat-mcp-server --client claude

Manual Compilation and Setup

1. Clone the source repository:

git clone https://github.com/Verodat/verodat-mcp-server.git cd verodat-mcp-server

1. Install necessary packages and generate production assets:

npm install npm run build

1. Configure the AI Client (e.g., Claude Desktop): Locate or generate the client's configuration file:
2. MacOS path: ~/Library/Application Support/Claude/claude_desktop_config.json
3. Windows path: %APPDATA%/Claude/claude_desktop_config.json

Integrate the server configuration payload detailed below into this file.

Verodat Service Connection

1. Provision an account at verodat.com.
2. Secure an active AI API token through the Verodat administrative console.
3. Securely inject this token into your client configuration.

Configuration Schema

The server necessitates specific parameters for secure API access and endpoint resolution. Define the following structure in your client's configuration file:

{ "mcpServers": { "verodat-consume": { "command": "node", "args": [ "path/to/verodat-mcp-server/build/src/consume.js" ], "env": { "VERODAT_AI_API_KEY": "[YOUR_SECURE_API_KEY]", "VERODAT_API_BASE_URL": "https://verodat.io/api/v3" } } } }

Capability Granularity Configuration

For targeted deployment, you may invoke only a subset of tools by specifying the corresponding compiled JavaScript entry point within the client configuration:

• Read-Only Access: Utilize consume.js (8 operational functions).
• Schema Creation Capable: Employ design.js (9 operational functions).
• Full Data Administration: Select manage.js (10 operational functions).

To enable all operational tiers simultaneously, define them as separate entries, as illustrated:

{ "mcpServers": { "verodat-consume": { ... configuration for consume.js ... }, "verodat-design": { ... configuration for design.js ... }, "verodat-manage": { ... configuration for manage.js ... } } }

Environmental Parameters

• VERODAT_AI_API_KEY: The mandatory token required for authenticated interaction with the Verodat service.
• VERODAT_API_BASE_URL: The endpoint URI for the Verodat REST interface (defaulting to "https://verodat.io/api/v3" if omitted).

Operational Command Reference

The bridge exposes the following distinct MCP functionalities:

// Account and Context Services get-accounts // Enumerate organizational entities get-workspaces // List active operational spaces get-queries // Fetch persisted analytical requests

// Data Structure and Content Services create-dataset // Provision new data containers get-datasets // Index available datasets get-dataset-output // Retrieve underlying dataset records get-dataset-targetfields // Obtain attribute definitions upload-dataset-rows // Append new data points to a dataset

// AI Interaction Services get-ai-context // Retrieve operational environment context execute-ai-query // Initiate on-demand data analysis

Selecting the Appropriate Deployment Profile

• Data Ingress/Egress Only: Configure the service using the consume.js profile.
• Structure Initialization Required: Deploy with the design.js profile.
• Data Modification Allowed: Activate the manage.js profile for full capability.

Security Posture

• All requests must be authenticated using the provided API key.
• Rigorous input validation mechanisms are enforced to safeguard against malformed data payloads.

Engineering & Codebase Structure

The application is implemented in TypeScript, structured logically into:

• Function Handlers: The core business logic implementing each external tool.
• Communication Layer: Protocols managing the I/O stream with the invoking AI client.
• Schema Validation: Utilizing Zod for ensuring data integrity and conformance across all interfaces.

Diagnostic Utilities

Debugging standard stdio communication can be complex. We supply an integrated MCP Inspector tool to aid in diagnosis:

npm run inspector

This command generates a network address for browser-based debugging tools.

Collaboration

We encourage community engagement! Contributions via Pull Requests are highly valued.

Licensing

Refer to the project's LICENSE file for usage rights.

Support Channels

• Comprehensive Documentation: Verodat Documentation Portal
• Issue Tracking: GitHub Repository Issues
• Community Forum: Verodat Organizational Discussions

---

WIKIPEDIA NOTE: Business operational tools encompass the entire spectrum of applications, methodologies, control mechanisms, and analytical solutions utilized by enterprises to maintain market relevance, adapt to shifting dynamics, and elevate organizational effectiveness. These tools span departmental needs, covering domains such as strategic foresight, workflow optimization, record keeping, personnel management, strategic deliberation, oversight, and performance benchmarking.

== Evolution of Business Software == This category originated with basic Management Information Systems (MIS), evolving into comprehensive Enterprise Resource Planning (ERP) suites, followed by the integration of Customer Relationship Management (CRM) functionalities, and culminating in today's cloud-native business management platforms. Value maximization hinges critically on two factors: the efficacy of the implementation process and the judicious selection and tailoring of the chosen tools to the organization's unique operational contours.

== Dominant Methodologies (2013 Benchmark) == A widely cited 2013 analysis highlighted prevalent global management practices, including:

Strategic Foresight Client Relationship Management (CRM) Workforce Sentiment Analysis Comparative Performance Analysis (Benchmarking) Performance Measurement Frameworks (Balanced Scorecard) Core Competency Identification Operational Outsourcing Organizational Transition Programs Logistics Chain Governance Defining Corporate Intent (Mission/Vision) Target Market Stratification Integrated Quality Control (TQM)