Claude Tools / MCP Servers / Team Knowledge
Illustrative tool or service connector
Team Knowledge
Searches and retrieves pages from a shared documentation workspace.
networkTemplate signals
Status
Draft
Audit
Not run
Collection
MCP Servers
Anatomy
What it contains
- A local stdio command or remote server URL
- A tool and resource surface exposed to the agent
- Credential, environment, and network configuration
Lifecycle
How it works
- The client starts or connects to the server
- The server advertises tools and resources
- The agent calls a selected tool
- The server returns structured results
Audit lens
What Zebonastic would check
- Credentials remain outside prompts and source files
- Egress destinations and write capabilities are clear
- Tool schemas constrain dangerous parameters
Content preview
Example configuration
Editable starter content9 lines
{
"mcpServers": {
"example-service": {
"command": "node",
"args": ["dist/server.js"],
"env": { "API_TOKEN": "${EXAMPLE_API_TOKEN}" }
}
}
}Related