Skip to main content
Glama
Earth616 Vocabulary Service

Earth616 Vocabulary Service

by LA3D

Earth616 MCP Vocabulary Service

A Model Context Protocol (MCP) server for accessing the Earth616 Defense Supply Chain and Documentation Ontology (DSCDO).

Quick Start

Option 1: Local Development

  1. Build the service:

    npm install
    npm run build
  2. Test the service locally:

    # Test that it starts up
    node dist/index.js
    # Should output: "Earth616 MCP Vocabulary Server running on stdio"
    # Press Ctrl+C to exit
  1. Start the full stack:

    npm run docker:up

    This starts:

    • Nginx server on port 8080 (serving example ontology files)

    • MCP vocabulary service (connected to nginx)

  2. Test the stack:

    # Test ontology server
    curl http://localhost:8080/health
    
    # View example files
    curl http://localhost:8080/example/
  3. View logs:

    npm run docker:logs
  4. Stop the stack:

    npm run docker:down
  5. Connect to Claude Desktop:

    Copy the configuration from claude_desktop_config.json to your Claude Desktop configuration file:

    • Mac: ~/Library/Application Support/Claude/claude_desktop_config.json

    • Windows: %APPDATA%\Claude\claude_desktop_config.json

    Or merge with existing config:

    {
      "mcpServers": {
        "earth616-vocab": {
          "command": "node",
          "args": ["/full/path/to/earth616_mcp_vocab_service/dist/index.js"],
          "env": {
            "NODE_ENV": "development"
          }
        }
      }
    }
  6. Test in Claude Desktop:

    After restarting Claude Desktop, you should be able to use these tools:

    • hello_vocab - Simple test tool

    • get_ontology_info - Basic ontology information

    • test_ontology_server - Test connectivity to the ontology file server

    • list_example_files - List available example files

Related MCP server: BioOntology MCP Server

Current Status

This is a minimal MCP server with Docker integration. Available tools:

  • hello_vocab: Echo back a message (testing connectivity)

  • get_ontology_info: Get basic information about the Earth616 ontology

  • test_ontology_server: Test connectivity to the ontology file server

  • list_example_files: List available example ontology files

The Docker setup provides:

  • nginx: Serves ontology files with proper content types

  • MCP service: Connects to nginx and provides vocabulary access

  • Health checks: /health endpoint for service monitoring

Next Steps

Following the iterative approach outlined in VOCAB_SERVICE_PLAN.md, we'll gradually add:

  1. File-based vocabulary term lookup

  2. URI resolution capabilities

  3. W3C PROF Profile navigation

  4. Complete vocabulary dataset access

  5. Cross-layer navigation tools

Development

Local Development

  • npm run dev - Watch mode for development

  • npm run build - Build TypeScript

  • npm start - Run the built server

Docker Development

  • npm run docker:build - Build Docker image

  • npm run docker:up - Start full stack (detached)

  • npm run docker:down - Stop full stack

  • npm run docker:logs - View MCP service logs

  • npm run docker:test - Quick health check test

Development Workflow

  1. Make changes to src/index.ts

  2. npm run docker:up to test with full stack

  3. Use Claude Desktop tools to test functionality

  4. npm run docker:logs to debug issues

  5. npm run docker:down when done

The server runs on stdio and communicates with Claude Desktop via the MCP protocol. The Docker setup simulates the full production environment locally.

Available Tools

18 tools
discover_shapesB

Discover and list all available SHACL shapes with their URIs and descriptions

Inputs: format, version.

explore_vocabularyB

Get a comprehensive overview of all available Earth616 vocabulary resources, files, and capabilities

Inputs: no named parameters.

get_layer_infoA

Get information about available CogitareLink layers and their URI mappings

Inputs: layer.

get_ontology_infoB

Get basic information about the Earth616 ontology

Inputs: no named parameters.

get_shape_contentC

Get the full content of a specific SHACL shape file with proper dereferencing

Inputs: shape_name (required), format, version.

hello_vocabB

Simple hello world tool for Earth616 vocabulary service

Inputs: message (required).

list_all_filesB

List all available files across ontologies, contexts, shapes, and examples with descriptions

Inputs: version.

list_context_releasesA

List available JSON-LD context release versions

Inputs: no named parameters.

list_example_filesB

List available example ontology files

Inputs: no named parameters.

list_ontology_releasesB

List available ontology release versions

Inputs: no named parameters.

list_shape_releasesA

List available SHACL shape release versions

Inputs: no named parameters.

read_context_fileB

Read a specific JSON-LD context file from a release

Inputs: filename (required), version.

read_example_fileB

Read the contents of a specific example file

Inputs: filename (required).

read_ontology_fileB

Read a specific ontology file from a release

Inputs: filename (required), version.

read_shape_fileA

Read a specific SHACL shape file from a release

Inputs: filename (required), version.

resolve_termB

Resolve a vocabulary term to its definition, context, and related information

Inputs: term (required), format, include_hierarchy.

resolve_uriB

Resolve a persistent URI to its deployment URL with content negotiation

Inputs: uri (required), accept.

test_ontology_serverA

Test connectivity to the ontology file server

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools have clear distinct purposes, but list_all_files overlaps with specific list functions and some read functions are similar across file types, causing minor potential confusion.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun snake_case pattern for the most part, though 'hello_vocab' uses a non-verb greeting, slightly breaking the pattern.

    Tool Count4/5

    18 tools is reasonable for a vocabulary service covering multiple file types and operations, though slightly on the higher side; each tool seems justified.

    Completeness4/5

    The tool set covers browsing and reading of ontologies, contexts, shapes, and URIs, but lacks a tool to list all vocabulary terms, leaving a minor gap in discoverability.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers