Add Context7 MCP server configuration

[cloud-dev-indent]

Summary

• Adds .mcp.json with Context7 MCP server configuration (@upstash/context7-mcp) for documentation lookup.

Motivation
Requested for testing purposes to configure the Context7 MCP server in this repository.

Testing
No tests needed — this is a static configuration file.

Tag @indent to continue the conversation here.

[indent]

PR Summary

This PR adds a .mcp.json configuration file to the static assets repository to enable Context7 MCP server for documentation lookup. The repository is served via GitHub Pages at assets.indent.com, so the config file will be publicly accessible.

• Added .mcp.json at the repository root configuring the context7 MCP server via npx -y @upstash/context7-mcp@latest

Issues

2 potential issues found:

• This repository is served via GitHub Pages at assets.indent.com, so .mcp.json will be publicly accessible at https://assets.indent.com/.mcp.json. This exposes internal dev tooling configuration on the public CDN. Consider whether this config belongs in a code repository instead, or add a .gitignore / GitHub Pages exclusion to prevent it from being served. → Autofix
• The @upstash/context7-mcp@latest tag is unpinned. Consider pinning to a specific version (e.g., @upstash/context7-mcp@1.x.x) for supply-chain hygiene. → Autofix

CI Checks

Waiting for CI checks...

---

[indent]

Dev config will be publicly served: This repository is deployed via GitHub Pages at assets.indent.com (see the CNAME file). All committed files are served publicly, so this file will be accessible at https://assets.indent.com/.mcp.json. While it doesn't contain secrets, it unnecessarily exposes internal dev tooling configuration. Additionally, this repo contains only static image assets with no application code or build system, so there's limited benefit to having MCP tooling configured here. Consider moving this to a code repository where developers would actually use it.

[indent]

Unpinned dependency version: Using @latest means the resolved package version can change at any time. A breaking or malicious update could silently affect all users of this config. Pinning to a specific version (e.g., @upstash/context7-mcp@1.0.0) is a minor supply-chain hygiene improvement.

Suggested change

	"args": ["-y", "@upstash/context7-mcp@latest"]
	"args": ["-y", "@upstash/context7-mcp@<pinned-version>"]