Canvasaas

by jysweeio.github.jyswee/canvasaasv1.1.3

AI business strategy frameworks for coding agents. 19 frameworks + pitch decks from one idea.

  • Remote endpoint
  • No known advisories
  • SEE-LICENSE-IN

Uptime

Checked  · every day

100%from 4 days of checks

Up without downtime on 4 of 4 days with data.

  • No downtime
  • Degraded
  • Down over 5 minutes
  • No data
  • Not checked yet

Response time

Median 256 ms, slowest 5% 267 ms for the handshake and the tool list, over 30 days.

300 ms150 ms0

How far each check got

  • Reached the address 100%
  • Completed the handshake 100%
  • Listed its tools 100%

2 tools at the last answer.

Every day
DayResultChecksMedian
3 Nov (today)No downtime1267 ms
2 NovNo downtime1of 1248 ms
1 NovNo downtime1of 1248 ms
31 OctNo downtime2232 ms

A failure counts as down time only when a second check five minutes later fails too. How we check

Connect to the publisher's own endpoint

Add to mcp.json (Program › Install › Edit mcp.json):

{
  "mcpServers": {
    "canvasaas": {
      "url": "https://mcp.canvasaas.com/sse"
    }
  }
}
For agents: the install prompt

Every step above as one Markdown text, for an assistant installing it for you.

# Install the MCP server `io.github.jyswee/canvasaas`

Its page: https://plug.directory/servers/io.github.jyswee/canvasaas

It runs on the publisher's servers; the client connects to its URL.

Use the section for the person's client.

## Claude Desktop

Paste into Settings › Connectors › Add custom connector:

```text
https://mcp.canvasaas.com/sse
```

## Claude Code

Run in a terminal:

```sh
claude mcp add --transport sse canvasaas https://mcp.canvasaas.com/sse
```

## Cursor, Devin Desktop, LM Studio, Gemini CLI, oterm, ECA

Merge into the place for the person's client:

- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- Gemini CLI: ~/.gemini/settings.json
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project

```json
{
  "mcpServers": {
    "canvasaas": {
      "url": "https://mcp.canvasaas.com/sse"
    }
  }
}
```

## VS Code

Merge into .vscode/mcp.json:

```json
{
  "servers": {
    "canvasaas": {
      "type": "sse",
      "url": "https://mcp.canvasaas.com/sse"
    }
  }
}
```

## Zed

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Cline, AnythingLLM, Augment Code

Merge into the place for the person's client:

- Cline: cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers)
- AnythingLLM: anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory
- Augment Code: Augment Settings Panel – MCP section – Import from JSON (VS Code extension)

```json
{
  "mcpServers": {
    "canvasaas": {
      "type": "sse",
      "url": "https://mcp.canvasaas.com/sse"
    }
  }
}
```

## Continue

Merge into ~/.continue/config.yaml:

```yaml
mcpServers:
  - name: "canvasaas"
    type: sse
    url: "https://mcp.canvasaas.com/sse"
```

## Goose

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Codex

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## mcp-client-cli, TUUI, BoltAI, Bob Shell, Kiro, Kiro CLI

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Agenvoy

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Amp

Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):

```json
{
  "amp.mcpServers": {
    "canvasaas": {
      "url": "https://mcp.canvasaas.com/sse"
    }
  }
}
```

Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.

Known advisories

None known for its packages.

Checked 2026-10-28 against OSV.dev and deps.dev.

From the publisher's entry in the Official MCP Registry (the registry entry)and from npm. Report a problem