Connect a service
In Connections, pick a service under Service to pre-fill its name, endpoint and sign-in method: Linear, Notion, Todoist, ClickUp, Sentry, Atlassian (Jira, Confluence), GitHub, monday.com or SeggWat. GitHub and monday.com need a personal access token.
For any other service, keep Custom and enter a name and the service's HTTPS MCP endpoint. Choose Sign in with the service, then Sign in. Approve access on the service's sign-in page; you will return to Smiet with the connection saved.
For services that use API tokens, choose Access token or no authentication, paste the bearer token, then choose Connect. Leave the token empty for a public server. Use Test to check a saved connection and its available actions.
OAuth access tokens refresh automatically when the service supports refresh tokens. If access expires or is revoked, choose Reconnect to sign in again. Your connection and action history are retained.
For SeggWat, use https://seggwat.com/mcp and sign in with the service.
Alternatively, use an Organization Access Token from SeggWat's
Settings → API Tokens. Paste only the token, without Bearer .
You can then use actions such as list_projects and create_feedback.
Connections belong to your Smiet account. Tokens are encrypted on the server and are not returned to the browser. Disconnect removes the saved connection; to revoke the token itself, use the connected service's settings.
Calendar and tasks (CalDAV)
Smiet can add Task and Event notes to your own calendar server: Nextcloud, iCloud, Fastmail or Radicale. In Connections, under Calendar and tasks (CalDAV), enter the server's HTTPS URL, your username and an app password, then choose Connect. For Nextcloud, create the app password under Settings → Security → Devices & sessions → Create new app password; the server's address is enough, Smiet finds the calendars itself. The server must be reachable over public HTTPS.
Choose where Tasks go to and where Events go to, then Save. Tasks become to-dos (VTODO) with their due date and priority; events become calendar entries (VEVENT) with start, end and location. An event without an end lasts one hour, or the whole day for a date without a time.
On a note's page, Add to tasks or Add to calendar sends it right away. Turn on Add tasks automatically after triage or Add events automatically after triage to send new notes without a click: tasks that name no project and events with a start time, the same notes the iPhone app would export. A sent note is marked processed. Sending the same note again never creates a duplicate.
Ideas go to takes a WebDAV folder on the same account. In Nextcloud, open
Files → Settings (bottom left) and copy the WebDAV address, then append
the folder, for example
https://cloud.example.com/remote.php/dav/files/USERNAME/Notes/. The folder
must already exist. Each idea becomes one Markdown file with frontmatter (id,
captured, tags); the file name is the idea's title plus a short id, so
saving it again never creates a duplicate. On a note's page use Save as
note, or turn on Save ideas automatically after triage. With an Obsidian
vault synced through Nextcloud, point it at a vault folder and it works as an
Obsidian inbox.
Context-based triage
Connect SeggWat and your project board in Connections. Under Discovered projects, Smiet reads each service's projects and available actions. Matching project names work automatically; no mapping is required. Use Refresh projects after adding projects or changing a server's tools.
Triage combines the note's intent, project and surrounding context:
- “Got feedback for Highlander that it looks good” suggests creating feedback in SeggWat's Highlander project.
- “Fix Highlander's login bug by Friday” suggests creating an issue in the board's Highlander project.
- “A customer reported broken login in Highlander” remains feedback. An explicit request to investigate that complaint becomes a task.
Each note has Triage findings: the extracted intent and project, highlighted quotes from the note, and a short explanation. Matching details and log shows matching services/actions, discovery problems, the model and timestamp, and the saved JSON. Earlier runs are retained. These are model-generated findings for review; the quotes are checked against the original note. They appear on the note's page; open the note from the inbox. For split captures, findings retain the original capture so evidence remains traceable.
For an existing note, choose Analyze context or Re-analyze. Re-analysis updates its classification and suggestions and may split a compound capture. It never sends an external write. Finish or discard any prepared action first.
Choose Review suggestion, check or complete the fields, then Review action and Confirm and create. The reviewed arguments stay fixed until you choose Edit. An ambiguous or unverifiable match requires manual selection under Actions; it is never sent automatically.
The OXIDT project board's create_issue needs a workflow state. Smiet reads
list_issue_states and lets you choose a real state. Due dates and priorities
that cannot be set during creation are retained in the description; setting
those board fields is a separate action. Feedback creation saves SeggWat's
returned feedback ID in Activity. Successful suggested actions mark the note
processed and retain the full service response in Action history.
Feedback aliases (optional) lets you associate a shorthand such as “HL” with a discovered SeggWat project. Existing saved mappings remain usable as aliases, but do not force every Highlander note to go to SeggWat.
Discovery currently supports argument-free list_projects, get_projects,
listProjects and projects_list, returning projects with IDs and names. Servers
with other discovery schemas or required organization arguments show a notice
and remain usable through manual Actions. Catalogs are cached for 15 minutes.
If discovery fails, Smiet shows the last successful catalog with a notice and
retries discovery the next time it is needed.
Project names, aliases and tool schemas are included in the configured triage
model's context; credentials and unrelated issue contents are not.
Run an action
- Open a note from the inbox and go to its Actions section.
- Choose the connection and an action from that server's tool list.
- Fill in the fields. Matching fields from the note's triage payload and its text may be prefilled; check them before continuing. Use Edit as JSON for nested arguments or schemas that need more than the generated fields.
- Choose Review action, then Run action to send the displayed arguments.
- Read the saved response in Action history. Use Done when the note's work is complete; looking up projects, for example, does not complete a note.
For feedback, run list_projects first, then use the chosen project's ID in
create_feedback with your message. Other task and calendar services expose
their own tools and required fields; Smiet discovers these when you connect.
When a response is missing
Outcome unknown means the call may have completed without a final response. Check the connected service before creating another action. Refresh results reloads the saved result without sending the action again. Repeated requests to run the same reviewed action do not dispatch it again.
After checking the service, choose Resolve unknown outcome. Record whether the item was created, include its ID/link or details of your check, and confirm the original request is no longer running. Recording a created item completes the suggested delivery. Recording that nothing was created allows a new draft. This step saves your checked outcome; it does not send an action.
Server setup and current scope
Set a persistent ENCRYPTION_KEY before saving connections that use tokens.
Generate a 32-byte base64 key with openssl rand -base64 32. Keep it with the
server's other secrets and retain it when restoring the database.
This version supports remote Streamable HTTP MCP servers at public HTTPS URLs, with OAuth sign-in, bearer-token, or no authentication. OAuth services must publish authorization metadata, support PKCE S256, and accept either dynamic client registration or Smiet's client metadata document. Services requiring manually registered OAuth client credentials are not supported yet.
Set BASE_URL to the exact address used to open Smiet. The callback is
{BASE_URL}/api/connections/oauth/callback on HTTPS, or {BASE_URL}/callback
on HTTP localhost for development. Providers may require this exact URL in an
allowlist. Sign-in must finish in the same browser within ten minutes.
Local stdio processes, private-network endpoints, and background MCP task tracking are not supported. AI suggestions run only after you review and confirm them.