Northwestern Digital Collections API MCP MCP Server

Northwestern Digital Collections API MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Northwestern Digital Collections API MCP directly instead of describing what you should do. Agent integration with the Northwestern University Libraries Digital Collections API.

What you get

The env.json file contains environment variable values for the lambda functions defined in the API for use in local development. You can create an env.json file containing the values to run the API against your dev data by running:

What the assistant can call

Once Northwestern Digital Collections API MCP is connected, these are the calls the assistant has available:

• Meadow — View and edit information about a specific Work in the Index

Configuration and credentials

You will need 4 environment variables: CHAOS_CONFIG, NEXT_PUBLIC_DCAPI_ENDPOINT, WORK_ID, FILE_SET_ID. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Northwestern Digital Collections API MCP's toolset — Meadow — is a fair guide to whether it matches your workflow.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the northwestern digital collections api mcp mcp server does with a few real requests.