MCP server that provides architecture design expertise to AI coding agents
Architecture Pattern MCP is an MCP integration. MCP server that provides architecture design expertise to AI coding agents.
The published oci package is docker.io/olkowa/architecture-pattern-mcp:1.1.3. Its declared MCP transport is stdio.
The package declares GENERATOR_API_KEY (required): API key for the generator LLM (LiteLLM provider).; GENERATOR_PROVIDER: LiteLLM provider prefix, e.g. openai, anthropic, openrouter, minimax.; GENERATOR_MODEL: Model name, combined as / via LiteLLM.; GENERATOR_BASE_URL: OpenAI-compatible base URL (LiteLLM api_base).; PATTERN_DIRECTORY: Directory with -pattern.json files. The image bakes the 40-pattern catalogue at /app/pattern.; EMBEDDER_PROVIDER: Embedding backend for pattern retrieval: tei, openai, ollama, vllm or hosted_vllm.; EMBEDDER_BASE_URL (required): Required: the dense retrieval leg embeds the 40-pattern catalogue during startup warmup and the server refuses to start when the endpoint is unreachable. OpenAI-compatible embeddings endpoint ending in /v1: on the Docker host use http://host.docker.internal:8080/v1 (add --add-host=host.docker.internal:host-gateway on Linux); on a shared Docker network use http://pattern-tei-embed:8080/v1.; EMBEDDER_API_KEY: API key for the embedder. Keyless TEI accepts any non-empty value; use 'not-needed' there.; RERANKER_BASE_URL (required): Required: pattern retrieval runs a mandatory TEI cross-encoder rerank. On the Docker host use http://host.docker.internal:8080; on a shared Docker network use http://pattern-tei-rerank:8080..
This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository. This profile uses version 1.1.3 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related developer tools MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| GENERATOR_API_KEY | API key for the generator LLM (LiteLLM provider). | Yes |
| GENERATOR_PROVIDER | LiteLLM provider prefix, e.g. openai, anthropic, openrouter, minimax. | Check documentation |
| GENERATOR_MODEL | Model name, combined as / via LiteLLM. | Check documentation |
| GENERATOR_BASE_URL | OpenAI-compatible base URL (LiteLLM api_base). | Check documentation |
| PATTERN_DIRECTORY | Directory with -pattern.json files. The image bakes the 40-pattern catalogue at /app/pattern. | Check documentation |
| EMBEDDER_PROVIDER | Embedding backend for pattern retrieval: tei, openai, ollama, vllm or hosted_vllm. | Check documentation |
| EMBEDDER_BASE_URL | Required: the dense retrieval leg embeds the 40-pattern catalogue during startup warmup and the server refuses to start when the endpoint is unreachable. OpenAI-compatible embeddings endpoint ending in /v1: on the Docker host use http://host.docker.internal:8080/v1 (add --add-host=host.docker.internal:host-gateway on Linux); on a shared Docker network use http://pattern-tei-embed:8080/v1. | Yes |
| EMBEDDER_API_KEY | API key for the embedder. Keyless TEI accepts any non-empty value; use 'not-needed' there. | Check documentation |
| RERANKER_BASE_URL | Required: pattern retrieval runs a mandatory TEI cross-encoder rerank. On the Docker host use http://host.docker.internal:8080; on a shared Docker network use http://pattern-tei-rerank:8080. | Yes |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
Use Microsoft’s Playwright MCP server to navigate pages, inspect accessibility snapshots, fill forms and capture browser screenshots.
Connect GitHub MCP to repositories, issues and pull requests with GitHub’s hosted service or a locally run server.
Use the Supabase MCP server to inspect database schemas, query project data and retrieve docs through a project-scoped connection.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.