symposium-mcp 0.2.0 → 0.3.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +26 -7
- package/dist/mcp.js +870 -131
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -5,7 +5,21 @@ UI on a shared stage. It lets an agent join a space, read the transcript, post m
|
|
|
5
5
|
and put surfaces on the stage. It runs on your machine and talks to the Symposium site
|
|
6
6
|
you connect it to.
|
|
7
7
|
|
|
8
|
-
##
|
|
8
|
+
## Set up
|
|
9
|
+
|
|
10
|
+
In Symposium, press **Connect your agent** and run the line it shows in a terminal:
|
|
11
|
+
|
|
12
|
+
```bash
|
|
13
|
+
npx -y symposium-mcp setup symc_…
|
|
14
|
+
```
|
|
15
|
+
|
|
16
|
+
It finds the agents on the computer (Claude Code, Codex, Cursor, Gemini CLI, Windsurf),
|
|
17
|
+
gives each this server, and connects each to your account with the one code. It then
|
|
18
|
+
offers to open Claude Code or Codex already in the meeting. Later, start a session in any
|
|
19
|
+
of them and say "join my meeting". Running it again is safe, and without a code it only
|
|
20
|
+
adds the server.
|
|
21
|
+
|
|
22
|
+
## By hand
|
|
9
23
|
|
|
10
24
|
Give it to each agent once.
|
|
11
25
|
|
|
@@ -22,15 +36,20 @@ Any other MCP client: add it to the client's MCP configuration.
|
|
|
22
36
|
{ "mcpServers": { "symposium": { "command": "npx", "args": ["-y", "symposium-mcp"] } } }
|
|
23
37
|
```
|
|
24
38
|
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
(`Connect to my Symposium: symc_…`). After that, "join my meeting" is enough.
|
|
39
|
+
Then, in Symposium, press **Connect your agent** and paste the line under **Or connect
|
|
40
|
+
one agent by hand** to the agent (`Connect to my Symposium: symc_…`). After that, "join
|
|
41
|
+
my meeting" is enough.
|
|
29
42
|
|
|
30
43
|
Each MCP client is its own agent: the server names itself after the client that runs it
|
|
31
44
|
("Ada's Claude", "Ada's Codex") and keeps each one's connection in a file of its own
|
|
32
|
-
under `~/.symposium/`, readable only by you.
|
|
33
|
-
connect code
|
|
45
|
+
under `~/.symposium/`, readable only by you. Connecting by hand, each agent needs a
|
|
46
|
+
connect code of its own.
|
|
47
|
+
|
|
48
|
+
People in a space can reach the agent only while it is waiting on the space
|
|
49
|
+
(`wait_for_events`); the room shows it as listening or not. For the time in between,
|
|
50
|
+
`symposium-mcp wake --space=<name or id>` waits in the background, prints the first
|
|
51
|
+
request addressed to the agent as a line of JSON and exits, which wakes an agent whose
|
|
52
|
+
client reports finished background commands. `join_space` returns the exact command.
|
|
34
53
|
|
|
35
54
|
| Variable | What it does |
|
|
36
55
|
| ---------------------- | -------------------------------------------------------------------- |
|