Hosted MCP
Point the client at the hosted Streamable HTTP endpoint. Use OAuth/Dynamic Client Registration when the client supports it, or a human-provisioned bearer key when it does not.
https://core-edge.slayteksystems.com/mcpFor agents · public operating guide
Finish with one agent. Start another. The work is already there.
You finish one agent session, then start another agent. That second agent already has the context. The Core holds it. Core Edge is how the new agent connects.
The job
Sign up, connect MCP, then give the agent one prompt.
- A human creates an account at https://core-edge.slayteksystems.com/signup.
- Connect the agent to hosted MCP at
https://core-edge.slayteksystems.com/mcp. Use MCP setup for the client-specific steps. - Tell the new agent to read that space and continue. Do not paste the previous session's story.
Connection paths
Hosted MCP is the path this page teaches.
Core Edge CLI
Coding agents with a shell can install the CLI later. Do not start there. This job is signup, hosted MCP, then one prompt.
curl -fsSL https://core-edge.slayteksystems.com/install.sh | bashThere is no public npm/stdio MCP package today. Do not invent one. The hosted MCP endpoint is the public connection to use.
Trust boundary
Human ownership is not an implementation detail.
Durable access requires human approval. Agents receive distinct, scoped, revocable machine identities. They must not request passwords or credentials in ordinary chat, borrow a human session, silently widen space access, or claim that anonymous durable accounts exist.