CamMicGo SEO MCP

Your Google data, your LinkedIn profile and five scientific sources, inside your AI assistant.

Free · Open source (MIT) · Remote MCP for Claude, ChatGPT and other clients · Local MCP for Windows, macOS and Linux

Website · Connect your assistant · Your account · Privacy · CamMicGo

                       

What it is

CamMicGo SEO MCP is a Model Context Protocol server. It lets your AI assistant work with your own accounts: Search Console, Google Analytics 4, YouTube and YouTube Analytics, Google Ads, Drive, Gmail, Calendar, LinkedIn publishing, and five scientific sources. Ask in plain language, for example "Which queries lost clicks this month?", "Where do my YouTube viewers come from?" or "Post this on my LinkedIn", and the assistant calls the right tool.

• Read-only by default. Write permissions are optional boxes that you tick yourself.

• Nothing is published, spent or trashed without your explicit yes. The assistant always shows the exact preview first.

• Your own accounts, kept separate. Google calls use your own Google Cloud project. LinkedIn connects in one click with the shared CamMicGo app, or with your own LinkedIn app. Each connection only acts for its owner, and secrets are encrypted on the server and never shown to the assistant.

• The website and every guide are available in 11 languages: English, French, Spanish, German, Portuguese, Italian, Russian, Chinese, Japanese, Korean and Arabic.

Related MCP server: Google Search Console MCP Server

Services

Other Google services:

• Docs, Sheets and Slides are readable through the Drive tools.

• Tasks, Contacts, Classroom, Chat and Apps Script are available as OAuth permissions only, with no dedicated tools yet.

Get started: step-by-step guides

Every setup has a complete illustrated guide on the website.

Remote MCP in four steps

1. In your assistant, add the custom connector https://seo.cammicgo.com/api/mcp (Streamable HTTP with OAuth).

2. Sign in to CamMicGo with your email and authorize the assistant.

3. On your account, save your Google Cloud OAuth client: Web application, with the redirect URI https://seo.cammicgo.com/api/auth/google/callback. Tick the APIs you want, then click Connect Google.

4. Ask: "List my Search Console sites and my GA4 properties."

YouTube blocks cloud servers, so the remote MCP fetches transcripts through a device you pair: the Android app or the desktop relay for Windows, macOS and Linux. Ask your assistant for a pairing code. The local MCP doesn't need a paired device.

Local MCP in short

Requires Node.js 22+ and Git.

git clone https://github.com/CamMicGo/cammicgo-seo-agent.git
cd cammicgo-seo-agent
npm install
npm run install:local   # guided: Google Desktop OAuth client, sign-in, agent registration
npm run local:doctor    # checks credentials and tokens

• OAuth client: the local MCP uses a Desktop app OAuth client from your own Google Cloud project. Tokens stay encrypted on your computer.

• Register it in your assistant: npm run agent:setup -- claude (or gemini, cursor) adds the stdio server to Claude Desktop, Gemini CLI or Cursor.

• More help: full guide on the website, with troubleshooting in docs/LOCAL-MCP-INSTALL.md.

cammicgo: terminal and local MCP for NotebookLM

npm link                # once, in the cloned folder: adds the "cammicgo" command
cammicgo login          # sign in to NotebookLM in a dedicated Chrome window
cammicgo setup vscode   # or claude, claude-code, cursor, windsurf, gemini, all
cammicgo notebook list

The full NotebookLM toolset of the Android app (notebooks, sources, Studio, chat, notes, research, collections, sharing, downloads), YouTube transcripts into notebooks, from the terminal or any MCP client, without the phone or the CamMicGo server. See docs/CAMMICGO-CLI.md.

LinkedIn: two ways to connect

• Simple (one minute): on your account, click Connect LinkedIn and allow with your own LinkedIn account. You don't need a LinkedIn Page or a developer app.

• Advanced, with your own LinkedIn app: create a developer app (LinkedIn requires a Page for it) and add the Share on LinkedIn and Sign In with LinkedIn using OpenID Connect products. Register the redirect URL https://seo.cammicgo.com/api/auth/linkedin/callback, then save the app's keys on your account. CamMicGo then uses your app instead of the shared one. Illustrated guide: seo.cammicgo.com/setup/linkedin.

• Who can post where: each connection only lets the person who authorized it post on their own profile. The owner of the shared app cannot post on your profile, and nobody can post on a company Page through CamMicGo.

• Local MCP: LinkedIn publishing is part of the remote MCP, because after sign-in LinkedIn sends you back to a CamMicGo web address. Add the remote connector next to your local one to publish on LinkedIn.

• Reuse the style of your previous posts: LinkedIn doesn't let apps read your past posts. Paste one or more of them into the conversation and ask for a new one in the same format. For your whole history, use LinkedIn's Get a copy of your data (Settings & Privacy › Data privacy): its Shares.csv file lists all your posts. Attach it to the conversation or put it in your Google Drive.

• Self-hosting: set LINKEDIN_CLIENT_ID and LINKEDIN_CLIENT_SECRET to offer a shared app. Otherwise, an administrator can share the app saved in their own account (account page, LinkedIn section).

Full walkthrough: seo.cammicgo.com/setup/linkedin

Tools

Remote MCP: https://seo.cammicgo.com/api/mcp

✎ marks a tool that writes something. These tools always work in two steps: an exact preview first, then your explicit yes.

Local MCP (stdio, read-only)

The local server has these tools:

• Account and properties: service_info, find_google_properties

• Search Console: list_search_sites, search_performance, seo_keyword_opportunities

• Google Analytics 4: list_ga4_properties, ga4_top_pages, ga4_countries

• YouTube: youtube_my_channels, youtube_my_videos, youtube_video_metrics, youtube_get_transcript (the local server fetches transcripts itself)

• Google Calendar: calendar_list, calendar_upcoming_events

• Scientific sources: the same nine science_* tools as the remote server

• NotebookLM (after cammicgo login): the same 51 NotebookLM tools as the remote server, executed directly on the computer — see docs/CAMMICGO-CLI.md

Bing Webmaster Tools

Each user saves their own Bing Webmaster Tools API key at /account (Bing Webmaster Tools › Settings › API access › API Key). The key is encrypted with AES-256-GCM in cmg_bing_keys, shown back only as a hint, and never returned to the AI assistant.

Tools: bing_sites, bing_search_performance, bing_queries, bing_pages, bing_crawl, bing_sitemaps, bing_url_info, bing_inbound_links, bing_keyword_research (read-only) and bing_submit_urls, bing_submit_sitemap (URLs of the user's own site only, within Bing's daily quota).

Safety: nothing happens without your yes

• Two steps for every write. LinkedIn posts, YouTube uploads, Drive trash and Google Ads campaigns all work the same way. The first call returns the exact preview and a confirmation token, bound to your account and to the exact content (including the bytes of an attached file). The token can be used from 10 seconds to 15 minutes after the preview. Only your explicit yes, in a new message, carries out the action. One confirmation publishes once, even if the assistant retries.

• Google Ads: campaigns are always created paused, with a total budget that is never exceeded. You enable them yourself in Google Ads.

• Google Drive: files are moved to the trash only, never deleted permanently, and drive_restore_file undoes it.

• Secrets stay on the server. Google and LinkedIn client secrets, API keys and tokens are encrypted on the server (AES-256-GCM). They are never returned to the browser or to the assistant.

• No access to arbitrary files. The assistant cannot read files on the server or on your computer. Files come only from your Drive, a public https link or the conversation.

Quotas

Privacy

See the privacy page.

• What is stored: CamMicGo keeps only what the service needs: your encrypted credentials and tokens, and usage counters.

• Disconnect at any time: from your account, from your Google account permissions, or from LinkedIn's permitted services.

Development

npm install
cp .env.example .env.local   # fill in your own values, never commit them
npm run dev                  # http://localhost:3000
npm test                     # unit tests
npm run lint
npm run build
npm run test:mcp:local       # local MCP protocol smoke test (no Google call)

Stack: Next.js 15 (App Router), mcp-handler, zod, Supabase (sign-in and encrypted storage) and Vercel. Pushes to main deploy to production.

Main environment variables:

• Google and sessions: APP_BASE_URL, GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, SESSION_ENCRYPTION_KEY

• Supabase: SUPABASE_URL, SUPABASE_SECRET_KEY, NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY, ENABLE_SUPABASE_MCP_AUTH

• Optional science keys: OPENALEX_API_KEY, SEMANTIC_SCHOLAR_API_KEY, NCBI_API_KEY

• Optional shared LinkedIn app: LINKEDIN_CLIENT_ID, LINKEDIN_CLIENT_SECRET

• Allowance overrides: MCP_DAILY_LIMIT, MCP_MINUTE_LIMIT, MCP_MINUTE_TOTAL_LIMIT, MCP_GLOBAL_DAILY_LIMIT, MCP_ADMIN_DAILY_LIMIT

More documentation

• Connecting agents

• Local MCP installation

• cammicgo command line and local NotebookLM

• Local transcript agent

• Google modules and security

• Quotas and launch

• Supabase MCP OAuth and the consent screen

• Plugin description

License and notices

The original code is published under the MIT license. Third-party dependencies keep their own licenses. The country map uses react-svg-worldmap (MIT). Country photos come from Wikimedia Commons and are credited in the app (for example, Japan: SRP1998, CC BY-SA 4.0).

Google, YouTube, Google Ads, LinkedIn, OpenAlex, Semantic Scholar, arXiv, PubMed and HAL are trademarks of their respective owners. Their names and logos only identify the services this project connects to. CamMicGo is not affiliated with or endorsed by them.

Made by CamMicGo: free webcam, microphone, headphone and device tests.