Skip to main content
Glama
meowrain

Cambridge Dictionary MCP Server

by meowrain

Dictionary Server

A dictionary server supporting the Model Context Protocol (MCP).

Retrieves word meanings from the Cambridge Dictionary.

Adding MCP to Command Line

To integrate the MCP server into your command line, add the following configuration:

"mcp-server-cambridge-dict": {
  "command": "npx",
  "args": ["-y", "mcp-server-dictionary"],
  "disabled": false
}

Related MCP server: Dictionary By Api Ninjas

Features

  • Seamless integration with Claude and other AI assistants via the MCP protocol.

  • Robust dictionary query tools.

  • Retrieves word meanings from the Cambridge Dictionary.

Development

Install Dependencies

Install the required dependencies:

npm install

Build the Server

Build the server for production:

npm run build

Development Mode

Enable auto-rebuild during development:

npm run watch

Running the Server

Start the MCP server with the following command:

npm run start:mcp

Testing with MCP Inspector

To test the server, use the MCP Inspector:

npm run inspector

MCP Response Specification

This server adheres to the MCP response specification.

Tool Response

A successful word query returns the following format:

{
  "content": [
    {
      "type": "text",
      "text": "Word query result (in JSON format)"
    }
  ]
}

Error Response

In case of an error, the response format is:

{
  "content": [
    {
      "type": "text",
      "text": "Error message"
    }
  ],
  "isError": true
}

API Documentation

lookup_word

Fetches the pronunciation, definition, and example sentences for a word.

Parameters

  • word (string): The word to query.

Returns

Detailed information about the word, including pronunciation, definition, and example sentences.

Available Tools

1 tool
lookup_wordD
ParametersJSON Schema
NameRequiredDescriptionDefault
wordYesThe word to look up

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

  1. 1 tool updatev1.0.0
    • First observedlookup_word

TDQS

D1.7/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool 'lookup_word' stands alone with a clear, singular purpose.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'lookup_word' follows a clear verb_noun pattern.

Tool Count2/5

A single tool for a dictionary server is too minimal for the apparent scope, as it lacks basic operations like searching, listing, or handling multiple languages. This severely limits functionality and feels incomplete.

Completeness1/5

The tool surface is severely incomplete for a dictionary domain, offering only word lookup with no descriptions, synonyms, antonyms, examples, or related operations. This will cause frequent agent failures for common dictionary tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers