Dc Api

Name: Dc Api
Author: nulib

by nulibcommunityv2.10.10

An MCP server that exposes Northwestern University Library's Digital Collections API as tools for AI assistants. It supports stdio and HTTP transports and can be configured with API base URLs and optional secrets path settings.

From the registry: Agent integration with the Northwestern University Libraries Digital Collections API

GitHub Repository

Install & configure

Prerequisites

required
Install Node.js 24+
Node.js version 24 or newer is required to run the server.
required
Install mise
The wrapper script bin/run.sh uses mise to activate the correct runtime.
https://mise.jdx.dev/
required
Install project dependencies
Install the server's npm dependencies before running it locally.
```
$ npm install
```

Install in your client

Paste into the AI you're chatting with — it will figure out the rest

Please install the `dc-api` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Install Node.js 24+** — Node.js version 24 or newer is required to run the server.
- **Install mise** — The wrapper script bin/run.sh uses mise to activate the correct runtime. (https://mise.jdx.dev/)
- **Install project dependencies** — Install the server's npm dependencies before running it locally. Run: `npm install`

Canonical MCP server config (stdio transport):
- command: `bin/run.sh`
- args: []
- optional environment variables:
  - `DC_API_BASE`: Base URL for the Digital Collections API. (example: `<your-dc-api-base-url>`)
  - `DC_IIIF_BASE`: Base URL for the IIIF API. (example: `<your-iiif-base-url>`)
  - `SECRETS_PATH`: Base secrets path to load configuration from AWS Secrets Manager. (example: `<your-secrets-path>`)

Note: The README also documents an HTTP mode via `cd src && npm run http` on port 3000, but it does not provide a canonical MCP HTTP endpoint URL shape for client configuration. The simplest documented MCP client configuration uses stdio via `bin/run.sh`.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.

Note: The README also documents an HTTP mode via `cd src && npm run http` on port 3000, but it does not provide a canonical MCP HTTP endpoint URL shape for client configuration. The simplest documented MCP client configuration uses stdio via `bin/run.sh`.