fimo 2.9.0-staging.8 → 2.10.0-staging.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/assets/skills/fimo/SKILL.md +1 -1
- package/assets/skills/fimo-cli/SKILL.md +1 -2
- package/assets/skills/fimo-cli/references/integrations.md +50 -71
- package/assets/skills/fimo-cli/references/mcp.md +3 -10
- package/assets/skills/fimo-cli/references/site-checks.md +5 -3
- package/assets/skills/fimo-studio/SKILL.md +3 -3
- package/assets/skills/fimo-studio/references/integrations.md +103 -0
- package/dist/cli/bundle.json +2 -2
- package/dist/cli/index.js +229 -91
- package/package.json +8 -8
- package/templates/astro/package.json +3 -3
- package/templates/nextjs/package.json +4 -4
- package/templates/react-router/package.json +5 -5
- package/templates/sveltekit/package.json +3 -3
- package/templates/vite/package.json +5 -5
- package/assets/skills/fimo-studio/references/connections.md +0 -51
|
@@ -39,7 +39,7 @@ Pick by task:
|
|
|
39
39
|
- Writing code — schemas/forms, generated clients, labels, framework adapters, rendering primitives → `fimo-code`
|
|
40
40
|
- Site creation, local setup, cloning, and CLI workflows — init, push, deploy, sync, labels, domains, analytics → `fimo-cli`
|
|
41
41
|
- AI agent setup — connect Claude Code, Codex, Cursor, or another agent → `fimo-cli` (`references/agent-setup.md`)
|
|
42
|
-
-
|
|
42
|
+
- Integrations — Search Console, Slack, or an MCP server: add, inspect, search, or run its tools → `fimo-cli` (`references/integrations.md`)
|
|
43
43
|
- The Fimo Studio dashboard / web app UI → `fimo-studio`
|
|
44
44
|
- Migrating an existing site into Fimo → `fimo-migration`
|
|
45
45
|
|
|
@@ -104,7 +104,7 @@ Load the matching reference when the user's request fires its trigger. Recipes t
|
|
|
104
104
|
- "Schedule a command / cron / nightly publish / recurring checks / `fimo schedules`" → `references/schedules.md`
|
|
105
105
|
- "Set env vars / configure API keys / add project secrets / local `.env.local` / `fimo vars` / `fimo secrets`" → `references/project-vars-and-secrets.md`
|
|
106
106
|
- "React to form submissions / publish changes / analytics reports / media activity / send events to Resend, Slack, GitHub, Zapier, or an HTTP endpoint / configure or debug outbound webhooks" → `references/webhooks.md`
|
|
107
|
-
- "
|
|
107
|
+
- "Use a connected app / Google Search Console / clicks, impressions, rankings, keywords from Google / Google Analytics / GA4 users, sessions, traffic sources, key events / enable provider tools / integrations / add, inspect, search, or run an MCP server / `fimo integrations` or `fimo mcp`" → `references/integrations.md`
|
|
108
108
|
- "Firecrawl / scrape a public website / competitor research / agent web research" → `references/integrations.md` **+ load `references/integrations/firecrawl.md`**
|
|
109
109
|
- "Check credits / credit balance / can I keep using AI / billing credits / running low / how many credits are left" → `references/credits.md`
|
|
110
110
|
- "List history / create a restore point / recover content and code / restore a previous version / snapshot usage or retention" → `references/history.md`
|
|
@@ -117,7 +117,6 @@ Load the matching reference when the user's request fires its trigger. Recipes t
|
|
|
117
117
|
- "Invite a collaborator / add Marc / share with client" → `references/invite.md`
|
|
118
118
|
- "Login / log out / who am I / switch organization" → `references/account.md` — note: switching **org** is `fimo orgs switch`; bare `fimo switch` changes the active **Fimo Branch** (see `references/branches.md`)
|
|
119
119
|
- "Install Fimo for my agent / fimo skills install / set up Claude Code, Codex, or Cursor for Fimo" → `references/agent-setup.md`
|
|
120
|
-
- "Add, inspect, search, or run a remote MCP server / use `fimo mcp`" → `references/mcp.md`
|
|
121
120
|
- "Refresh / update installed Fimo skills / fimo skills sync / agent missing the latest Fimo conventions" → `references/agent-setup.md`
|
|
122
121
|
- "Update / upgrade the project's fimo packages / move to a new Fimo release / `fimo update`" → `references/update.md`. Never edit `fimo` or `fimo-*` versions directly in `package.json`; `fimo update` keeps package pins and codemods aligned.
|
|
123
122
|
- "Report a Fimo problem or blocking feature request / contact Fimo support / a Fimo API or command keeps failing / a documented argument is rejected / a supported operation needs an undocumented workaround / a Fimo API is abnormally slow / a confirmed missing capability blocks completion or forces a fragile or heavily manual workaround" → `references/support.md`
|
|
@@ -1,94 +1,73 @@
|
|
|
1
1
|
# Integrations
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Integrations are the outside services a site can use. There are three kinds, all used the same way:
|
|
4
4
|
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
5
|
+
- **Integrations an organization connects**, such as Google Search Console, Google Analytics, and the MCP integrations Semrush, Ahrefs and DataForSEO (SEO data). An organization admin connects one from **Integrations** in Fimo Studio; a site manager turns it on for a site and fills its settings. An MCP integration's tools come live from the provider's server.
|
|
6
|
+
- **MCP integrations from the catalog**, such as PostHog and Resend. An organization admin signs in from Studio, or adds the integration's API key once with `fimo integrations connect <integration> --token-stdin`. Then turn it on per site with `fimo integrations enable <integration>`.
|
|
7
|
+
- **MCP servers your organization adds** with `fimo integrations add`. Their tools come live from the server.
|
|
8
8
|
|
|
9
|
-
|
|
9
|
+
`fimo integrations` uses the integrations turned on for the current site. Slack is an integration too, managed from Studio's Slack settings. Every credential is stored encrypted by Fimo and never printed back to the CLI.
|
|
10
10
|
|
|
11
|
-
|
|
12
|
-
fimo integrations list
|
|
13
|
-
fimo integrations info firecrawl
|
|
14
|
-
fimo integrations status firecrawl
|
|
15
|
-
```
|
|
11
|
+
Firecrawl and Fal are Fimo's built-in services, on Fimo's key and Fimo credits. They are no longer available to new sites: a site that already uses one keeps it, sees it in `fimo integrations list`, and runs it as before (`references/integrations/firecrawl.md`). Never offer them to a site that does not have them.
|
|
16
12
|
|
|
17
|
-
|
|
13
|
+
## Commands
|
|
18
14
|
|
|
19
|
-
|
|
15
|
+
| Command | Does |
|
|
16
|
+
| ------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
17
|
+
| `fimo integrations list` | Every integration the site could use, with its state: `on`, `needs <setting>`, `off for this site`, or `not installed`. Inside an agent session, the integrations that session may use. |
|
|
18
|
+
| `fimo integrations info <integration>` | The integration's guide: when it helps, how to read its numbers, its rules. Read it before an integration's first run. |
|
|
19
|
+
| `fimo integrations tools [integration] [--search <words>] [--tool <key>]` | Tools of the integrations that are on. `--search` keeps the best few matches with the start of what each does; `--tool` shows one tool with its input schema, before you run it. |
|
|
20
|
+
| `fimo integrations run <integration> <tool> --input '<json>'` | Run one tool. `--input` also takes `@file.json` or `-` for stdin. `--approval <code>` runs a change a person allowed. |
|
|
21
|
+
| `fimo integrations settings <integration> [--set key=value]` | Show the site's settings for an integration, or change one. A choice must be one the connected account offers. |
|
|
22
|
+
| `fimo integrations enable <integration>` / `disable <integration>` | Turn an integration on or off for this site. |
|
|
23
|
+
| `fimo integrations status <integration>` | The site's setup state for an integration. |
|
|
24
|
+
| `fimo integrations connect <integration> --token-stdin` | Add the organization's API key for an integration such as PostHog or Resend (organization admins) and turn it on for this site. Running it again replaces the key. |
|
|
25
|
+
| `fimo integrations add <name> --url <mcp-url>` | Add an MCP server for the organization and turn it on here. Options: `--auth`, `--header`, `--token-stdin`, `--headers-stdin`. |
|
|
26
|
+
| `fimo integrations reconnect <integration>` | Sign in to an OAuth MCP integration again. |
|
|
27
|
+
| `fimo integrations rotate <integration>` | Replace an MCP integration's credentials from stdin. |
|
|
28
|
+
| `fimo integrations remove <integration> --yes` | Remove an MCP server and its connection from every site (organization admins). |
|
|
20
29
|
|
|
21
|
-
|
|
30
|
+
`fimo mcp` still works but is deprecated: `mcp run` becomes `integrations run`, `mcp search` becomes `integrations tools --search`, `mcp add` becomes `integrations add`.
|
|
22
31
|
|
|
23
|
-
|
|
32
|
+
## Find the right tool
|
|
33
|
+
|
|
34
|
+
Search by what you need, not by integration name:
|
|
24
35
|
|
|
25
36
|
```bash
|
|
26
|
-
fimo
|
|
37
|
+
fimo integrations tools --search "search clicks impressions rankings"
|
|
38
|
+
fimo integrations info search-console
|
|
39
|
+
fimo integrations tools search-console --tool query_search_analytics
|
|
40
|
+
fimo integrations run search-console query_search_analytics --input '{"dimensions":["page"],"days":28}'
|
|
41
|
+
|
|
42
|
+
fimo integrations tools --search "users sessions traffic sources"
|
|
43
|
+
fimo integrations info google-analytics
|
|
44
|
+
fimo integrations run google-analytics performance_overview --input '{"days":28}'
|
|
27
45
|
|
|
28
|
-
fimo
|
|
29
|
-
fimo
|
|
30
|
-
fimo mcp run sentry <tool> --input '{"key":"value"}'
|
|
46
|
+
fimo integrations tools --search "keyword rankings backlinks"
|
|
47
|
+
fimo integrations tools --search "AI search citations share of voice"
|
|
31
48
|
```
|
|
32
49
|
|
|
50
|
+
## Add a remote MCP server
|
|
51
|
+
|
|
33
52
|
Automatic discovery connects public endpoints directly and opens the provider authorization page for OAuth servers.
|
|
34
53
|
Use `--auth none` to require a public endpoint, `--auth bearer --token-stdin` for a bearer token, or `--auth header
|
|
35
54
|
--header-name <name> --token-stdin` for a custom private header. A custom header value is sent exactly as piped, so it
|
|
36
|
-
carries any prefix itself. Fimo requires an HTTPS Streamable HTTP endpoint,
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
so native and MCP providers share one runtime policy surface.
|
|
40
|
-
|
|
41
|
-
## Integration References
|
|
42
|
-
|
|
43
|
-
Load the integration reference when the user names a specific integration:
|
|
55
|
+
carries any prefix itself. Fimo requires an HTTPS Streamable HTTP endpoint, encrypts credentials, assigns an
|
|
56
|
+
`mcp_`-prefixed key, and reads the server's current tools live. OAuth and manual headers are alternative grants and are
|
|
57
|
+
never sent together. Local stdio commands such as `npx` are not supported.
|
|
44
58
|
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
## Enable
|
|
48
|
-
|
|
49
|
-
```bash
|
|
50
|
-
fimo integrations enable firecrawl
|
|
51
|
-
fimo integrations enable fal
|
|
52
|
-
fimo integrations disable firecrawl
|
|
53
|
-
```
|
|
54
|
-
|
|
55
|
-
Bare enable uses the integration's default auth path. For Firecrawl and Fal that is the only path: Fimo credits, no key,
|
|
56
|
-
no connection, nothing to choose. `fimo integrations connect firecrawl` and `connect fal` are refused for that reason.
|
|
57
|
-
|
|
58
|
-
If an integration has no safe default auth path, bare enable stops with a repair command instead of guessing.
|
|
59
|
-
|
|
60
|
-
To bring your own Firecrawl or Fal account, add it as an MCP server (`fimo mcp add`), which is the generic path for any
|
|
61
|
-
server the user owns. It does not replace the built-in service.
|
|
62
|
-
|
|
63
|
-
## Connections
|
|
64
|
-
|
|
65
|
-
Use `connect` for provider accounts, workspaces, OAuth installs, and user-owned MCP servers. Connections live at the
|
|
66
|
-
organization level and are shared as capabilities, not as visible credentials. A project chooses one by enabling the
|
|
67
|
-
integration with `--connection <alias>`.
|
|
68
|
-
|
|
69
|
-
Set up Slack from **Project Settings > Connections** in Fimo Studio. Slack app creation and workspace approval require an explicit organization app choice, so the CLI does not guess one.
|
|
70
|
-
|
|
71
|
-
## Run
|
|
72
|
-
|
|
73
|
-
```bash
|
|
74
|
-
fimo integrations run firecrawl scrape --url https://example.com
|
|
75
|
-
fimo integrations run firecrawl scrape --url https://example.com --formats markdown,summary,links
|
|
76
|
-
fimo integrations run firecrawl search --query "Example Domain" --max-results 3 --include-domains example.com
|
|
77
|
-
fimo integrations run firecrawl map --url https://example.com --limit 20
|
|
78
|
-
fimo integrations run firecrawl crawl --url https://example.com --limit 3 --formats markdown
|
|
79
|
-
fimo integrations run firecrawl monitor.create --name pricing --url https://example.com/pricing --schedule hourly
|
|
80
|
-
fimo integrations run firecrawl monitor.list
|
|
81
|
-
```
|
|
59
|
+
## Changes need a yes
|
|
82
60
|
|
|
83
|
-
|
|
61
|
+
A tool whose `EFFECT` is not `read` changes data in the outside service, such as `submit_sitemap`. Run it only when the user asked for that change. Changes a person runs from their own CLI run straight away. Changes an agent runs need a person's yes, unless the site always allows that tool; paid actions always ask.
|
|
84
62
|
|
|
85
|
-
|
|
86
|
-
|
|
87
|
-
and country options; see the Firecrawl reference for the full command shape.
|
|
63
|
+
- `APP_APPROVAL_REQUIRED`: give the user the `approve_url`. When they allow the change there, Fimo shows them a one-time code: ask them to paste it, then run the same command, with the same input, plus `--approval <code>`. The code works once, for that exact call, within the hour.
|
|
64
|
+
- `APP_WRITE_BLOCKED`: the change cannot run this way. Do not retry; tell the user.
|
|
88
65
|
|
|
89
|
-
|
|
90
|
-
does not change the project default integration setup, and built-in services have no connection to name.
|
|
66
|
+
## Errors
|
|
91
67
|
|
|
92
|
-
|
|
68
|
+
- `needs property`: the site has not chosen which account data to use. A site manager picks it in Studio, Site settings, Integrations.
|
|
69
|
+
- `app_reconnect_required`: the provider revoked access. An organization admin reconnects the integration from Integrations.
|
|
70
|
+
- `not installed`: no one connected the integration yet. Tell the user what it would let you do; never ask for credentials.
|
|
71
|
+
- `Firecrawl and Fal are no longer available to new sites.`: the site never used that built-in service. Do not retry.
|
|
93
72
|
|
|
94
|
-
|
|
73
|
+
Set up Slack from **Settings > Integrations > Slack** in Fimo Studio.
|
|
@@ -1,5 +1,7 @@
|
|
|
1
1
|
# Remote MCP integrations
|
|
2
2
|
|
|
3
|
+
> **Deprecated.** `fimo mcp` still works but prints a warning: use `fimo integrations` instead (`references/integrations.md`). Changes ask for a person's yes the same way either way.
|
|
4
|
+
|
|
3
5
|
Use the `mcp` command group to connect a project to remote Model Context Protocol servers. Fimo stores the connection,
|
|
4
6
|
keeps its credential server-side, and makes the server's tools available through the same integration gateway as native
|
|
5
7
|
providers.
|
|
@@ -102,16 +104,7 @@ from stdin.
|
|
|
102
104
|
|
|
103
105
|
## Studio chat
|
|
104
106
|
|
|
105
|
-
|
|
106
|
-
through:
|
|
107
|
-
|
|
108
|
-
```bash
|
|
109
|
-
fimo integrations list
|
|
110
|
-
fimo integrations info mcp_sentry
|
|
111
|
-
fimo integrations run mcp_sentry search_issues --input '{"query":"open regressions"}'
|
|
112
|
-
```
|
|
113
|
-
|
|
114
|
-
Studio receives a frozen snapshot of the integrations enabled when the turn starts. It never receives the underlying
|
|
107
|
+
Studio chat finds and runs MCP apps with its own app tools, not with these commands. It never receives the underlying
|
|
115
108
|
credential or opens a direct connection to the remote server.
|
|
116
109
|
|
|
117
110
|
## Supported servers
|
|
@@ -59,9 +59,11 @@ fimo site links /pricing # each link on the page and
|
|
|
59
59
|
`internal-linking`, `hreflang`, `ai-readiness`, `structured-data`,
|
|
60
60
|
`citation`, `lifecycle`, `refresh`, `accessibility`, `mobile`, `consent`,
|
|
61
61
|
`privacy`. Without `--topic`, every topic runs.
|
|
62
|
-
- `--browser` renders in a real browser (needs `agent-browser`).
|
|
63
|
-
`accessibility`, `mobile`, `consent` and `privacy`; the other
|
|
64
|
-
HTML.
|
|
62
|
+
- `--browser` renders every page in a real browser (needs `agent-browser`).
|
|
63
|
+
Use it for `accessibility`, `mobile`, `consent` and `privacy`; the other
|
|
64
|
+
topics read HTML. A page whose HTML has no content before JavaScript runs (a
|
|
65
|
+
client-rendered site) is read in the browser without `--browser`; the output
|
|
66
|
+
says how many.
|
|
65
67
|
- The target is the Branch's hosted preview. While it builds, the command
|
|
66
68
|
waits up to 90 seconds. `prod` has no preview: check `--branch main`, or the
|
|
67
69
|
published address with `--url`.
|
|
@@ -36,7 +36,7 @@ Use plain, friendly language. Describe what users see, where they click, and wha
|
|
|
36
36
|
|
|
37
37
|
- **Header (desktop):** the site menu (site name; History is here) and the Branch switcher, then the workspaces: Chats, Getting started, Preview, Content, Assets, Analytics, Settings. Only workspaces the user can access appear. Workspaces that do not fit move into **More**. On the right: Earn free credits, Invite, Clone, Publish, and Merge on a Branch.
|
|
38
38
|
- **Phone:** bottom tabs for Chat, Preview and Settings. Invite, Earn free credits and Clone ("Work on this site locally") move into the site menu.
|
|
39
|
-
- **Settings:** General, Domains, Knowledge, SEO and Languages are listed directly. Models, Environments, Variables, Secrets, Schedules
|
|
39
|
+
- **Settings:** General, Domains, Knowledge, SEO, Integrations and Languages are listed directly. Models, Environments, Variables, Secrets, Schedules and Webhooks are under **Advanced settings**.
|
|
40
40
|
- **Shortcuts:** Alt+1 Preview, Alt+2 Content, Alt+3 Assets, Alt+5 Settings, Alt+E edit mode, Cmd/Ctrl+K command palette.
|
|
41
41
|
|
|
42
42
|
When a reference says "open X", X can be inside **More** on a narrow window.
|
|
@@ -59,7 +59,7 @@ Read the relevant reference file when the user's question matches a topic.
|
|
|
59
59
|
| Variables & Secrets | references/variables-and-secrets.md | "Where do I put an API key?", "Public or private variable?" |
|
|
60
60
|
| Schedules | references/schedules.md | "Recurring commands", "Run history", "Run now" |
|
|
61
61
|
| Webhooks | references/webhooks.md | "React to forms", "Send events to another service" |
|
|
62
|
-
|
|
|
62
|
+
| Integrations | references/integrations.md | "Connect a service", "Add an MCP server", "Slack channels" |
|
|
63
63
|
| Preview & Responsive | references/preview-and-responsive.md | "How does it look on mobile?", "How do I test sizes?" |
|
|
64
64
|
| Visual Editing | references/visual-editing.md | "Can I edit visually?", "How do I change colors?" |
|
|
65
65
|
| Version History | references/version-history.md | "How do I undo?", "How do I go back?" |
|
|
@@ -76,7 +76,7 @@ Read the relevant reference file when the user's question matches a topic.
|
|
|
76
76
|
| Adding images | Media Library, AI Chat, Edit Mode |
|
|
77
77
|
| Content/CMS | AI Chat, Media Library |
|
|
78
78
|
| Webhooks | Site secrets, Forms, Publishing |
|
|
79
|
-
|
|
|
79
|
+
| Apps | AI Chat, Site secrets |
|
|
80
80
|
| Schedules | Site secrets, Environments |
|
|
81
81
|
| API keys | Variables (private), Site secrets |
|
|
82
82
|
| Visual changes | Edit Mode (CMS content), AI Chat (layout, styling, and code changes) |
|
|
@@ -0,0 +1,103 @@
|
|
|
1
|
+
# Integrations
|
|
2
|
+
|
|
3
|
+
Integrations let a site use external services without exposing credentials to editors, chat, or agents. Studio, the CLI, and
|
|
4
|
+
agent chats all resolve the same integration state.
|
|
5
|
+
|
|
6
|
+
## Connect an integration for the organization
|
|
7
|
+
|
|
8
|
+
Open **Integrations** in the organization sidebar. It lists the integrations the organization already connected, then the ones still
|
|
9
|
+
available, with the number of sites each integration is on. Choose an integration to open its panel.
|
|
10
|
+
|
|
11
|
+
An organization admin connects an integration once for the whole organization, with no site needed:
|
|
12
|
+
|
|
13
|
+
- **Google Search Console** and **Google Analytics**: **Sign in with Google**, using a Google account that can see the
|
|
14
|
+
site's property, and approve the permissions Fimo lists.
|
|
15
|
+
- Integrations you sign in to: Ahrefs, DataForSEO, PostHog, Resend, Calendly and Cal.com. **Connect <integration>**
|
|
16
|
+
opens the provider's sign-in page and returns to Fimo. Finish in the same browser, signed in to Fimo as yourself.
|
|
17
|
+
Ahrefs, PostHog and Resend also offer **Use an API key instead**.
|
|
18
|
+
- Semrush connects with a Semrush API key: **Connect Semrush** opens the form with the `Authorization` header and
|
|
19
|
+
`Apikey ` prefix filled in.
|
|
20
|
+
- Slack: **Add to Slack** (in the organization's Integrations or a site's Integrations; each sign-in adds a workspace), then choose each
|
|
21
|
+
site's channels.
|
|
22
|
+
|
|
23
|
+
People who are not organization admins see **Copy link** instead, to send its link to an admin. The panel also shows
|
|
24
|
+
the connected account, with **Disconnect** (removes the integration from every site, with its settings and always-allowed tools), or **Reconnect** when the
|
|
25
|
+
provider stopped accepting it. A custom MCP server's **…** menu has **Rename** and **Delete server**. An MCP integration's
|
|
26
|
+
panel also shows its server and tools: see [Manage an MCP server](#manage-an-mcp-server).
|
|
27
|
+
|
|
28
|
+
### Site access
|
|
29
|
+
|
|
30
|
+
Under **Site access** in the integration's panel, choose **All sites** to give every site access, including sites created later,
|
|
31
|
+
or **Only select sites** and **Select sites**. Choose **Save**. A site left out loses the integration, and its managers cannot
|
|
32
|
+
turn it back on until an admin gives the site access again.
|
|
33
|
+
|
|
34
|
+
## Use an integration on a site
|
|
35
|
+
|
|
36
|
+
Open the site, then **Settings** → **Integrations**. The page lists the integrations **On for this site** first, then the **Available**
|
|
37
|
+
ones. Select an integration to open its panel. It says whether the integration is on for the site; the account, credentials and tools
|
|
38
|
+
live in the organization's **Integrations**:
|
|
39
|
+
|
|
40
|
+
- The switch turns the integration on or off for this site. People who manage the site can do this for any integration the site has
|
|
41
|
+
access to; others see it without changing it. An integration the organization has not connected says so and links to **Integrations**.
|
|
42
|
+
- Settings appear once the integration is on. Google integrations ask for the **Search Console property** or **Google Analytics
|
|
43
|
+
property** the site uses; Fimo suggests the one that matches the site's domain. An integration still missing a setting shows
|
|
44
|
+
**Finish setup** on its card, and its panel asks for the setting first; connecting from the site opens it there.
|
|
45
|
+
- **Manage the account and site access in Integrations** opens the organization page, for admins.
|
|
46
|
+
|
|
47
|
+
## Approve a change
|
|
48
|
+
|
|
49
|
+
Reads from an integration run straight away, and so do changes a person runs. When an agent wants to change data in an integration,
|
|
50
|
+
the chat shows a card with the integration, the tool and why it asks:
|
|
51
|
+
|
|
52
|
+
- **Allow** runs that exact change once.
|
|
53
|
+
- **Always allow** (for changes that are not paid actions) runs it and lets agents run that tool on this site
|
|
54
|
+
without asking again, in any chat.
|
|
55
|
+
- **Decline** stops it.
|
|
56
|
+
|
|
57
|
+
Paid actions ask every time. Changes asked from Slack, a routine, the CLI or the hosted MCP give a link to
|
|
58
|
+
**Settings** → **Integrations**, where the same card appears. For Slack, Fimo continues in the thread once it is allowed. A
|
|
59
|
+
routine cannot wait, so its link offers only **Always allow** and **Decline**, and its later runs make the change. For
|
|
60
|
+
the CLI or an AI client, **Allow** shows a one-time code to paste back; after **Always allow** the same call runs without
|
|
61
|
+
one. A request is answered once and an approval runs one exact change, both within an hour.
|
|
62
|
+
|
|
63
|
+
## Slack channels
|
|
64
|
+
|
|
65
|
+
Open **Slack**, then **Workspaces and channels**. Each Slack workspace the site answers in has a row. Open one to turn
|
|
66
|
+
it on for the site and choose the channels where Fimo answers mentions. Which sites use a workspace is Site access, and
|
|
67
|
+
disconnecting it is the account's **…** menu, both on Slack's page in the organization's Integrations, where **Add another
|
|
68
|
+
account** adds another workspace.
|
|
69
|
+
|
|
70
|
+
## Add an MCP server
|
|
71
|
+
|
|
72
|
+
Choose **Add MCP server** in a site's **Settings** → **Integrations** (anyone who manages the site), or on the organization's
|
|
73
|
+
**Integrations** page (organization owners and admins). A server added from a site shows in the organization's Integrations too:
|
|
74
|
+
|
|
75
|
+
1. Enter a **Name** and the server's **MCP URL**, a Streamable HTTP `https://` endpoint. A listed MCP integration, such as Semrush
|
|
76
|
+
or PostHog, fills both when you connect it from its panel.
|
|
77
|
+
2. **Connect with** shows the recommended sign-in path. Fimo checks the endpoint; public servers connect immediately,
|
|
78
|
+
while OAuth servers open their provider sign-in page and return after approval.
|
|
79
|
+
3. Open **Other ways to connect** when the server instead documents an access token, custom headers, or no
|
|
80
|
+
authentication.
|
|
81
|
+
4. In a site, **Use from another site** reuses a server another site already connected.
|
|
82
|
+
|
|
83
|
+
For **Paste an access token**, enter only the token; Fimo adds the `Bearer` scheme. For **Send custom headers**, enter
|
|
84
|
+
each complete value exactly as the server expects, including any prefix (`Authorization` with `Bearer abc123`). Fimo
|
|
85
|
+
encrypts every saved grant and never shows its private value again.
|
|
86
|
+
|
|
87
|
+
## Manage an MCP server
|
|
88
|
+
|
|
89
|
+
An MCP integration's panel in the organization's **Integrations** shows the server's address and its tools, grouped into reads,
|
|
90
|
+
changes and deletes; open a group, then a tool, for its full description. When the tools stop loading, the panel offers
|
|
91
|
+
the one repair for how the organization signs in:
|
|
92
|
+
|
|
93
|
+
- **Reconnect** signs in again for OAuth.
|
|
94
|
+
- **Update credentials** replaces a bearer token or the complete custom-header bundle after it stops working.
|
|
95
|
+
- **Retry connection** asks a public server for its tools again without touching any credential.
|
|
96
|
+
|
|
97
|
+
The account's **…** menu also has **Rotate credentials**, to replace a healthy token or header bundle. A custom
|
|
98
|
+
server's **…** menu has **Delete server**, which removes the server from the organization, for every site that uses it.
|
|
99
|
+
Only organization owners and admins can replace a shared credential or delete a server.
|
|
100
|
+
|
|
101
|
+
Only integrations turned on for the site are available to Studio chat and the Fimo CLI for this site. Agents should discover
|
|
102
|
+
them with `fimo integrations list`, inspect one with `fimo integrations info <integration>`, and run an allowed tool with
|
|
103
|
+
`fimo integrations run <integration> <tool>`.
|
package/dist/cli/bundle.json
CHANGED