AMBI
uk.slate-hq.registryv1.1.0Updated Oct 1, 2026
Save and retrieve your chosen context, manage shared workspaces, and track project time.
Overview
AI-generated overview
A remote MCP endpoint for saving and retrieving chosen context, managing shared workspaces, and tracking project time.
- What it does
- AMBI is a remote MCP server reached over streamable HTTP at a hosted endpoint. According to its registry description, it lets an assistant save and retrieve selected context, manage shared workspaces, and track time spent on projects. No individual tools are listed in the manifest, so the exact operations are not documented here.
- When to use it
- Consider it when you want an assistant to keep working context across sessions, coordinate shared workspaces, or log project time. It is less useful if you only need local file access or a single-session assistant.
- Requirements
- A remote MCP client that supports streamable HTTP, pointed at the provider's hosted endpoint. No packages, environment variables, or headers are declared, and the manifest declares no authentication.
Before you install
The manifest declares no authentication, so anyone who can reach the endpoint may be able to read or change stored context, workspaces, and time records. The server is hosted by a third party, so saved context and workspace data leave your machine. No tool list is published, so verify what it can write or delete before relying on it.
Installation
In SourceWeft
- Open AMBI in the dashboard and add it to a workspace.
- 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.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"ambi": {
"type": "http",
"url": "https://mcp.slate-hq.uk/ambi"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.1.0LatestOct 1, 2026