ARCH-Insight
com.arch-insightPublished by arch-insight.comOfficial publisherv0.1.7Updated Oct 25, 2026
Search and update ARCH-Insight: architecture fact sheets, applications, tickets, tasks, incidents.
Overview
ARCH-Insight is a remote MCP server that lets an assistant search and update architecture fact sheets, applications, tickets, tasks and incidents.
- What you can do
- Search and update architecture fact sheets and application records in ARCH-Insight, the enterprise architecture repository, so an assistant can look up how systems are documented and keep those records current. Search and update tickets, tasks and incidents, so an assistant can find work items and change their state. The manifest lists no individual tools, so the exact operations and their parameters are not documented here.
- When to use it
- Use it when an assistant needs to work with an organization's enterprise architecture documentation or its tickets, tasks and incidents, for example to look up how an application is described or to update a work item. It is not useful without an ARCH-Insight account.
- Requirements
- A remote MCP endpoint at arch-insight.com, reached over streamable HTTP. OAuth authentication is required, so the user needs an ARCH-Insight account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Installation
In SourceWeft
- Open ARCH-Insight in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.arch-insight%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"arch-insight": {
"type": "http",
"url": "https://arch-insight.com/mcp"
}
}
}Tools
0Version history
2- v0.1.7LatestOct 11, 2026
- v0.1.5Oct 11, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.