Skip to content
edisyledisyl

Search these docs from your AI tool

  • Antigravity
    {
  "mcpServers": {
    "edisyl-docs": {
      "serverUrl": "https://docs.edisyl.com/mcp"
    }
  }
}
  • Claude CodeCLI
    claude mcp add edisyl-docs https://docs.edisyl.com/mcp --transport http --scope user
  • CodexCLI
    codex mcp add --url https://docs.edisyl.com/mcp edisyl-docs
  • Cursor
    {
  "mcpServers": {
    "edisyl-docs": {
      "type": "http",
      "url": "https://docs.edisyl.com/mcp"
    }
  }
}
  • Gemini CLI
    gemini mcp add --transport http edisyl-docs https://docs.edisyl.com/mcp
  • Goose
    {
  "extensions": {
    "edisyl-docs": {
      "enabled": true,
      "name": "edisyl-docs",
      "type": "streamable_http",
      "uri": "https://docs.edisyl.com/mcp",
      "envs": {},
      "env_keys": [],
      "headers": {},
      "description": "",
      "timeout": 300,
      "bundled": null,
      "available_tools": []
    }
  }
}
  • JetBrains AI Assistant
    {
  "mcpServers": {
    "edisyl-docs": {
      "type": "http",
      "url": "https://docs.edisyl.com/mcp"
    }
  }
}

    Paste into Settings → Tools → AI Assistant → Model Context Protocol → Add → As JSON. Direct file writing isn’t supported — JetBrains stores this per-version as XML.

  • Junie (JetBrains)
    {
  "mcpServers": {
    "edisyl-docs": {
      "url": "https://docs.edisyl.com/mcp"
    }
  }
}
  • OpenCode
    {
  "mcp": {
    "edisyl-docs": {
      "type": "remote",
      "url": "https://docs.edisyl.com/mcp"
    }
  }
}
  • VS CodeCLI
    code --add-mcp '{"name":"edisyl-docs","type":"http","url":"https://docs.edisyl.com/mcp"}'
  • Windsurf
    {
  "mcpServers": {
    "edisyl-docs": {
      "serverUrl": "https://docs.edisyl.com/mcp"
    }
  }
}

    Supports both stdio and native HTTP connections.

Looking to ask a pack from your AI tool instead? That's a different server: see AI clients.

AI clients (MCP)

Connect edisyl to your AI client and ask a Knowledge Pack directly from chat or the tools you already use. Ask a pack a question, Teach it a fact, and Task its agents with longer work.

In addition to the CLI, edisyl also lets you reach your packs through MCP (Model Context Protocol). Everyone in your organization can ask questions and bring a pack’s knowledge into their existing workflow, in the AI tools they already use. Every client needs one URL:

https://api.edisyl.com/mcp

Add it, sign in with your edisyl account in the browser window that opens, and you’re connected. No API keys.

Set up your client

Section titled “Set up your client”

Claude

claude.ai and the Claude apps. Team and Enterprise owners can add it once for everyone. Set up Claude →

Microsoft 365 Copilot

A Copilot Studio agent, or an org-wide connector from the admin center. Set up Copilot →

Working with a pack from chat

What to say, what comes back, and what a refusal means. Read the guide →

What you can do once connected

Section titled “What you can do once connected”

Your client’s assistant gets these tools and calls them as you talk:

Say Tool Result
“Which packs can I use?” list_packs The packs in your org you can read.
“How many active wallets last week?” ask One cited answer over the pack’s knowledge and data.
“Show me the source for that.” read_document The document the answer cited.
“Remember that active means a swap in 30 days.” teach That fact, added to the pack for good.
“Research the new grant program and add it.” task The pack’s agents on longer work.
“Undo that teach.” forget The document and everything learned from it, removed.
“Check on that task.” action_get, action_list, action_events Status and progress of any ask, teach, or task.
“Ask this every Monday.” schedule_* Standing work the pack runs on its own.

Permissions

Section titled “Permissions”

Which tools work depends on your access to the pack, not on how you connected:

  • Any org member can list packs and ask the ones they can read.
  • teach needs contribute access on the pack. task needs steer access.
  • Anyone who can read a pack can list its schedules. Creating, firing, pausing, or deleting one needs steer access.

A forbidden response means you don’t have that permission. Ask the pack’s owner for access.

Not on MCP

Section titled “Not on MCP”

Connecting data sources, declaring objectives, editing PACK.md, and publishing a pack are done in the CLI. SQL, raw knowledge retrieval, and the semantic catalog are not exposed at all: ask covers them and returns its own evidence.

Report incorrect code

Please provide a detailed description of the incorrect code.