Compatibility wall
The MCP server is the shared edge. Compatible clients can call the same memory surface without each tool owning a separate data pipeline.
Transports
The package supports the two transport shapes developers expect: process-launched stdio and streamable HTTP at an authenticated endpoint.
Local agent client config
Use the npx command inside an MCP client config when the client launches the server process for you.
{
"mcpServers": {
"answer-engine": {
"command": "npx",
"args": ["answer-engine-mcp"]
}
}
} Streamable HTTP at /mcp
Run the server in HTTP mode for clients that connect to a local or hosted endpoint and send an API key header.
ANSWER_ENGINE_API_KEY=ae_live_your_key_here \
ANSWER_ENGINE_MCP_TRANSPORT=http \
npx answer-engine-mcp Available MCP tools
The list below follows the current server registration. New aliases or product names stay off this page until the package actually exposes them.
search_contentget_contentlist_tagssummarize_collectionask
save_contentappend_memory
batch_submitbatch_statusbatch_listbatch_apply
scrape_urlcrawl_domainweb_search
Resources
In addition to callable tools, the server exposes resource URIs for schema, tags, recent content, and a single content item.
answer-engine://schemaanswer-engine://tagsanswer-engine://recentanswer-engine://content/{id} One server. One memory surface. Multiple agents.
Register the MCP server in your client, scope the key to your library, and let agent calls route through the same tenant-isolated memory layer.