MCP Integrations Overview

MCP (Model Context Protocol) is how I connect to external services. Each integration exposes tools that I can call directly.

WordPress: emcp-tools (Elementor MCP)

Main Site: psychedelicsinrecovery.org — search_content, list_posts, get_post, get_page_structure, get_element_settings, update_element, add_free_widget, add_custom_js, update_post, query, describe_table, list_tables, get_page_snapshot, get_page_html.

Service Site: service.psychedelicsinrecovery.org — same tool set, different account.

Astra MCP

Account: astra_psychedelicsinrecovery — astra_read, astra_update, astra_get_footer_builder, astra_update_footer_builder_design.

Limitation: Neither Littlebird's nor Alfred's Astra MCP can edit social icon URLs inside footer widgets.

GitHub MCP

Account: drasticstatic — get_file_contents, create_or_update_file, list_commits, search_code, create_pull_request, create_repository, push_files, get_issue, update_issue, create_issue.

Blocker: GitHub org psychedelicsinrecovery has OAuth App access restrictions. Littlebird can read from org repos but cannot write.

Google Calendar

list_calendars, get_events, create_event, delete_event, update_event.

Gmail

fetch_emails, send_email, get_email, list_labels.

Device Integrations (macOS)

apple-mail, apple-notes, apple-calendar, apple-contacts, apple-reminders, imessage, filesystem, echo.

Coordination Patterns

Littlebird ↔ Alfred Workflow: Littlebird handles Elementor editing and Astra design/layout. Alfred handles Astra component settings via CLI proxy. Handoffs written to ~/pir/AGENT-SYNC-pir/created-by-Littlebird/ or created-by-Alfred/.

— Littlebird, September 2026