- weather/ — Python MCP server (copiato da skald/scripts), no auth, free API
- wikipedia/ — nuovo Python MCP server, Wikipedia API pubblica, no auth
- Entrambi: mcp_local, scope global, auth none, dipendenza httpx
- connectors.json: +2 connector (totale 7), auth:none aggiunto anche a SSH
- Deleted gmail_oauth_setup.py and gcal_oauth_setup.py (Skald handles OAuth)
- Removed google-auth-oauthlib dependency from requirements.txt and connector.json
- Simplified setup_instructions to point to Skald's OAuth flow
- Updated docstrings and error messages in *_mcp_server.py (no more refs to
*_oauth_setup.py, point to Skald OAuth / env-var instead)
- connectors.json: removed oauth_setup.py from files[], updated sha256 hashes
auth.deliver changes from as:file to as:env:
- Gmail: GMAIL_CREDS_JSON env var (Google authorized_user JSON)
- Gcal: GCAL_CREDS_JSON env var
mcp_config.env removed entirely — Skald injects the env var at runtime,
no path on disk needed.
Server scripts updated:
- Check GMAIL_CREDS_JSON / GCAL_CREDS_JSON env var first
- Use Credentials.from_authorized_user_info() instead of
from_authorized_user_file()
- Fall back to file-based loading for standalone/legacy use
- _persist_creds only writes to disk when _creds_path is set
gcal/verify.py: support GCAL_CREDS_JSON env var with shared _check_api()
Docs (SKALD.md): updated examples, field table, connector table.
connector.json: auth.deliver declares {as, format, path} so Skald
can write the Google authorized_user JSON without hardcoding paths.
connectors.json: gmail entry gains auth {type, provider, scopes}
for UI badge rendering without downloading the full manifest.
No changes to email, ssh, or tavily connectors.
Client-side page that captures the OAuth authorization code from
Google's redirect URL (?code=...) and displays it in a textarea
for copy-paste into Skald. Shows error details on failure.
Access at https://connectors.skaldagent.net/oauth/show.html
dguiducci