Recommended Free Tools
To connect an AI agent to Stack Internal, add the remote MCP endpoint for your workspace’s region, select Streamable HTTP, and complete the browser sign-in. A workspace administrator must enable MCP and connect the knowledge sources the agent needs. The documented MCP tools can search and retrieve knowledge; they are read-only.
Before you connect: check workspace access and sources
You need an account in the Stack Internal workspace. If the MCP endpoint is unavailable, ask an administrator to confirm that MCP access is enabled for the workspace. The administrator also needs to connect at least one data source; the Control Center guide lists Stack Internal Community, Google Docs, and Slack. The agent can retrieve only knowledge that is connected and indexed.
As an Amazon Associate I earn from qualifying purchases.
Administrators can review workspace controls and source configuration in the Stack Internal Control Center guide.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Connect an MCP-compatible client
1. Choose the regional endpoint
| Workspace region | Endpoint |
|---|---|
| Default region | https://mcp.stackinternal.com |
| EU-hosted workspace | https://mcp.eu.stackinternal.com |
Use the root URL exactly as shown: do not append /mcp or an API version. When your client asks for a transport, choose Streamable HTTP. The MCP Server Overview documents client-specific instructions; client labels and setup syntax can change, so follow the current instructions for your chosen client.
#1 Best Overall
2. Add the server
For command-line clients, Stack Internal documents these examples:
- Claude Code:
claude mcp add --transport http StackInternal https://mcp.stackinternal.com/ - Codex:
codex mcp add StackInternal --url https://mcp.stackinternal.com
For an EU-hosted workspace, substitute https://mcp.eu.stackinternal.com for the default-region host. Other listed clients include Claude Web, Copilot, Cursor, Gemini CLI, JetBrains AI Assistant, Visual Studio, Visual Studio Code, Windsurf, and Zed. Consult the official overview for the chosen client’s configuration.
3. Sign in and test retrieval
- Add the endpoint and select Streamable HTTP in the client’s MCP setup.
- When prompted, finish the browser sign-in flow.
- After sign-in, start a new conversation and ask a specific question about a connected source, such as “Search Stack Internal for the incident-response process.”
- For a useful result, ask the agent to show the source link. Check important decisions against the linked underlying source before acting.
The MCP Server Quickstart recommends treating returned nodes as source material and verifying important decisions against their linked sources.
What the Stack Internal MCP server lets an agent do
The documented MCP server has two read-only tools: search_nodes searches indexed knowledge, and get_node retrieves one node using an ID from search results. It does not create, edit, publish, vote on, or delete content. Stack Internal describes the server as enabling agents to securely access connected knowledge while preserving permissions, source identity, and governance; that is the product’s description, not an independent security certification.
Rank #3
If you need write operations or another automation capability, investigate the Stack Internal API separately. Its documentation lists scopes for reading and searching node content and metadata, as well as ingestion, deletion, connectors, analytics, and administration. Access requires an active workspace user, and a valid token by itself does not bypass tenant, role, or scope permissions. Grant only the scopes the integration needs. See The Stack Internal API.
Choose MCP or the API based on the job
| Route | Best fit | Access and capabilities |
|---|---|---|
| MCP server | An MCP-compatible assistant or coding agent that needs company-knowledge retrieval | Hosted regional endpoint, Streamable HTTP, and browser sign-in; documented operations are read-only search and node retrieval. |
| Stack Internal API | Custom integrations or workflows needing broader API operations | OAuth application and scoped API access; documented scopes include read, ingestion, administration, and other operations. |
Consider client compatibility, whether the workflow only reads or must write, required permissions, source coverage, and audit needs when selecting a route. The available MCP documentation does not establish write support.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How authentication and permissions work
Stack Internal documents an OAuth 2.1 sign-in process using Dynamic Client Registration and the authorization-code flow with PKCE. After sign-in, Stack Internal exchanges the external credential for its own signed access credential, tied to the authenticated user, organization, and permissions. MCP requests use that credential context for access decisions. Its MCP InfoSec overview and FAQ also describes HTTPS, short-lived credentials, protected signing-material storage, and activity records for events such as client registration and credential issuance.
Separately, the API InfoSec overview and FAQ says the default API access-credential lifetime is five minutes; the page does not state a publication year. It also says product-managed storage holds chat conversations and content records, and that when chat uses an AI provider, the question and relevant context needed for that request are sent to the provider, while the user’s product access credential is not. Those statements describe the API security FAQ and should not be assumed to cover every agent client or customer configuration.
Best Value
Troubleshoot connection and retrieval problems
- The client cannot reach the server: Check that you used the right regional host and the root URL, with no appended
/mcppath or API version. - The client rejects the connection: Confirm that it supports Streamable HTTP and that you selected that transport.
- Sign-in did not complete: Finish the browser flow, then retry from a new conversation.
- MCP is unavailable: Ask a workspace administrator to verify that MCP access is enabled.
- Search returns no relevant knowledge: Try shorter or more specific terms, use semantic search if your client offers it, and ask the administrator to confirm the relevant source is connected and indexed.
- An API call fails despite a valid token: Check active workspace-user status, tenant, role, and required scopes.
Stack Internal’s MCP Quickstart and API documentation cover these connection and access checks.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
