Nextdoor MCP Server
Posts, comments and recommendations for your Nextdoor business page.
Hosted MCP Server
npx add-mcp 'https://cotlet.dev/mcp/v1/nextdoor'Installs into Claude Code, Codex, Cursor and more
Documentation
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Nextdoor API and MCP server: Let your AI agent answer your Nextdoor neighbors.
Nextdoor has no MCP server, and its REST API is a closed beta: each application is reviewed case by case (checked 27 Oct 2026). Even an approved partner cannot read a business page's posts, recommendations or chats. Cotlet runs 13 Nextdoor tools hosted, over MCP for agents and REST for scripts.
Posts, comments and recommendations for your Nextdoor business page. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.
- Free 7-day trial, no card
- Unofficial, not affiliated with Nextdoor
- Page: https://cotlet.dev/integrations/nextdoor-api-mcp-server
What can you automate in Nextdoor?
- Thank neighbors who recommend you
- Write and publish the weekly post
- Answer questions under your posts
- Reply to Business Page chats
- Send your page link to customers
- Count recommendations and Faves
Does Nextdoor have an MCP server or an API?
- The Publish API can post, comment, edit and delete for a business profile. Its "Get your posts" call says "Business and Entity page users are not supported at the moment."
- Zapier has one Nextdoor trigger, New Lead from ad lead forms, and no actions. n8n has no Nextdoor node.
- The tools that post through the Publish API (Orlo, Social News Desk, Zencity) are sold to public agencies, not to local businesses.
| What you need | Publish API (approved partners) | GitHub MCP server | Cotlet |
|---|---|---|---|
| Publish a business post | Yes, once approved | Fills the form, you press Post | Yes, after your OK |
| Read your own posts and comments | Not for business pages | Neighborhood feed only | Yes |
| List and answer recommendations | No | No | Yes |
| Answer Business Page chats | No | No | Yes, in chats neighbors start |
| Open to any local business | Case by case | Yes, you run it | Yes |
Checked 27 Oct 2026. Sources: Nextdoor: applying for API access, Nextdoor API: Get your posts, Nextdoor: share using a business account, Nextdoor on Zapier
How does Cotlet connect to Nextdoor?
- Sign in to Nextdoor. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never keep your Nextdoor password, and no post, reply or chat reaches a neighbor before you approve it.
Connect Nextdoor to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Enable Nextdoor for agents. Make a Cotlet account, log in to Nextdoor in its Cloud Browser as the person who runs your Business Page, then press Enable for agents.
- Add the Cotlet address. Put https://cotlet.dev/mcp/v1 into your agent's MCP server or connector list.
- Let the agent in. Chat apps open a Cotlet sign-in. Editors, n8n and scripts send an API key from the console.
Nextdoor rides on https://cotlet.dev/mcp/v1 with every other app you turn on, so one connector covers all of them. Enabled Nextdoor after connecting? Refresh the connector to load its tools.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet-nextdoor \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet-nextdoor": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet-nextdoor]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: nextdoor_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: nextdoor_write
How to use the Nextdoor REST API
Create your Cotlet API key
Create a Cotlet API key with access to Nextdoor and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect Nextdoor in Cotlet and enable it for agents. Account access: Your own Nextdoor account with a claimed Business Page (owner, employee or authorized representative).
Make your first Nextdoor API request
REST:
curl https://cotlet.dev/api/v1/nextdoor/business-page \
-H "Authorization: Bearer $COTLET_API_KEY"
Read business page and apply the operation limits
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "nextdoor",
"tool": "get_business_page",
"result": {
"page_id": "pg_2204",
"name": "Clearwater Gutter Care",
"category": "Gutter cleaning",
"phone": "+1 555 0142",
"neighborhoods": [
"Maple Hill",
"Oak Park",
"Riverside"
],
"recommendations": 41,
"faves": 118
}
}
Returns the page the signed-in account manages. Use the neighborhoods it lists as the audience for create_post.
The call fails if the account has no claimed Business Page.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
Nextdoor workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Recommendations from the What neighbors say section, with author, neighborhood, text, date and your reply. Use list_recommendations in your configured business report. |
| Make | HTTP > Make a request | Comments on one of your posts, with author, neighborhood, text and whether you replied. Use list_comments in your configured business report. |
| Python or Node.js | REST API | Messages neighbors sent to your Business Page, with the last message and who wrote it. Use list_conversations in your configured business report. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads Nextdoor; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
Nextdoor API endpoints and MCP tools
Business Page and posts
Needs a claimed page; posting also needs a verified one. Posts take a title and text, no photos or polls. Nextdoor shows no view counts for business posts.
- Get Business Page (
get_business_page, read): Your page: name, category, contact details, neighborhoods, recommendation and Fave counts. - Get page share link (
get_page_share_link, read): The link to your Business Page from the Share menu, to send to customers who should leave a recommendation. - List posts (
list_posts, read): Business posts from your Business Page, newest first. - Get post (
get_post, read): One post: title, text, audience, reactions and comment count. - Create post (
create_post, write, asks first): Publish a business post to the neighborhoods you choose. - Delete post (
delete_post, write, asks first): Remove one of your business posts from Nextdoor.
Comments and recommendations
Replies are public and appear under your business name, not your personal profile.
- List comments (
list_comments, read): Comments on one of your posts, with author, neighborhood, text and whether you replied. - Reply to comment (
reply_to_comment, write, asks first): Reply as your business under a comment on one of your posts. - List recommendations (
list_recommendations, read): Recommendations from the What neighbors say section, with author, neighborhood, text, date and your reply. - Reply to recommendation (
reply_to_recommendation, write, asks first): Public reply from your business to a neighbor's recommendation.
Business Page chats
Only chats a neighbor opened. A business cannot write to a neighbor first.
- List conversations (
list_conversations, read): Messages neighbors sent to your Business Page, with the last message and who wrote it. - Get conversation (
get_conversation, read): Full message thread with one neighbor. - Send message (
send_message, write, asks first): Reply to a neighbor inside an existing Business Page conversation.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/nextdoor-api-mcp-server#tools
Who can see my Nextdoor session, and how do I revoke it?
- What we store. Your logged-in Nextdoor profile, AES-256-GCM encrypted, in Finland. Not the password.
- What your agent gets. The 13 Nextdoor tools for your page. No cookie, no login.
- What the session sees. What you see on Nextdoor: your page, its chats, and your own neighborhood feed.
- What no tool touches. Ads and budgets, verification papers, reports to Nextdoor, your password.
- If Nextdoor logs you out. You get an email with a link to log in again. We never do it for you.
- How to cut access. Disable for agents, reset the browser, or log out of Nextdoor there.
The session runs as a neighbor account that manages the page, so it could also read your home neighborhood. No tool reads the neighborhood feed. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results); there is no SOC 2 report or third-party pentest yet.
Is it against Nextdoor's terms? Account safety
develop, support or use software, devices, scripts, robots, or any other means or processes (including crawlers, browser plugins, and add-ons or any other technology) to scrape the Services or otherwise copy profiles and other data from the Services, including for inclusion in or to train large language models
The Agreement covers business use too, and it bans "bots or other automations" used to get into other members' accounts. An agent working in your own page is not named, but reading your page with software sits close to the clause above. Nextdoor can act on a Business Page without warning; the case on record is a member set to read-only for posting the same thing too often. We found no public case of an account closed for an automation tool (checked 27 Oct 2026). The risk is yours to weigh.
How we keep your account looking like you:
- Your own Nextdoor login and your own Business Page
- One Cloud Browser with its own IP and cookies
- Posts, replies, chats and deletes wait for your OK
- No tool reads the neighborhood feed or other businesses' pages
- If Nextdoor objects, we pause the Nextdoor tools for everyone within 24 h
Nextdoor counts repeated or templated posts as spam. Keep to one fresh post a week and a reply written for each neighbor, not one text pasted to all.
What happens when Nextdoor changes?
- 12 h between tests of the Nextdoor page tools
- $0 for a call to a Nextdoor tool paused for repair
Nextdoor redesigned its app in July 2025 and moves Business Page menus now and then. When a screen changes, we change the tool and your prompts keep working. status.cotlet.dev checks the site, console and API every 3 minutes.
Approvals, undo and mistakes
- Reads what is new. Recommendations since the last run, unanswered only.
- Sorts praise from complaints. A complaint gets a careful draft and stays with you.
- Waits for your OK. Each reply shows up in your Cotlet console first.
- Reports back. Who was thanked, what is held, what got no reply.
| Action | Undo |
|---|---|
| Publish a post | Edit it in Nextdoor, or delete_post after your OK |
| Delete a post | No, post it again by hand |
| Reply to a comment or recommendation | Edit or delete it in Nextdoor by hand |
| Send a chat message | No, the neighbor already has it |
5 of 13 tools ask first: create_post, delete_post, reply_to_comment, reply_to_recommendation and send_message. Every one of them is seen by neighbors or removes something. Reads and the page link run at once. Turning the wait off for one tool is up to you.
Fix a typo with Edit in Nextdoor, not by deleting and posting again: an edited post keeps its place in the feed.
MCP call:
{
"name": "create_post",
"arguments": {
"title": "Open house this Saturday",
"body": "Drop by 10:00 to 14:00 for free coffee and a look at the new workshop.",
"radius": 3
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/nextdoor/posts \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"title":"Open house this Saturday","body":"Drop by 10:00 to 14:00 for free coffee and a look at the new workshop.","radius":3}'
Response:
{
"post_id": "bp_8812046",
"status": "published",
"neighborhoods": 14,
"url": "https://nextdoor.com/p/yourname-open-house"
}
A script or cron job reaches the same tools over REST at /api/v1/nextdoor, one key, one price. create_post on a page Nextdoor has not verified yet fails, and a failed call costs nothing. The tools list shows the REST path of each tool.
How much does the Nextdoor MCP server cost?
About $15 a month for one local business with a weekly post and daily replies, 2,620 credits. The Nextdoor Business Page itself is free.
| Job | Calls | Credits |
|---|---|---|
| Thank new recommendations, weekly | 3 × 4 | 120 |
| Write and publish the weekly post | 2 × 4 | 80 |
| Answer comments and chats, weekdays | 4 × 22 | 880 |
| Page, recommendation and Fave count, weekly | 1 × 4 | 40 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 2,620 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Nextdoor ads stay billed by Nextdoor
The month is our example: one post a week, about 2 new recommendations a week and a weekday pass over comments and chats. Nextdoor publishes no per-page numbers, so the volume is our assumption. Dollars at the $29 pack rate.
Nextdoor MCP server on GitHub, Zapier or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| markswendsen-code/mcp-nextdoor | Six neighbor tools (feed, events, marketplace, recommendations search, a post draft) driving Nextdoor with Playwright on Browserbase. 1 star. | Your Nextdoor email and password in a config file. No Business Page tools, no license, last commit 14 Mar 2026. |
| RosenAdvertising/nextdoorads-mcp | 14 tools on the Nextdoor Ads API: campaigns, ad groups, creatives, reports. MIT, last commit 11 Oct 2026. | Ads only, and the Ads API needs Nextdoor's approval and an API agreement. |
| Pipedream Nextdoor Ads | Hosted MCP with 7 Ads API actions, in beta. | Ads only. Nothing for posts, recommendations or chats. |
| Zapier | New Lead trigger from Nextdoor ad lead forms, also as Zapier MCP. | No actions at all. |
| Orlo, Social News Desk, Zencity | Schedule and publish through the Publish API, with approvals. | Sold to public agencies, not to business pages. |
If you run ads, the Ads API servers above manage campaigns well, and Cotlet has no ad tools. If you are a city or a police department, an agency tool on the official API is the safer route. For a local business that wants its recommendations, comments and chats answered, nothing else on this list reaches the Business Page.
Who runs Cotlet
Behind Cotlet is Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Send questions about the Nextdoor tools to contact@cotlet.dev.
Nextdoor API and MCP: questions
How do I get access?
Create a free account at https://cotlet.dev, open Nextdoor under Integrations in the console and log in to Nextdoor in its Cloud Browser with the account that manages your Business Page. The trial starts when you sign up, no card asked.
Can it message neighbors first?
No. Nextdoor's help center says a business cannot message neighbors, and its self-promotion policy bans unsolicited promotional messages. send_message replies only in conversations a neighbor started.
Do I need a verified business to post?
Nextdoor asks casual service providers, such as dog walkers or babysitters, to verify with official business documents before they post to the neighborhood newsfeed. Verify in Nextdoor first; then create_post works.
Does Nextdoor have webhooks?
Not for business pages. The only event feed is the Zapier New Lead trigger for ad lead forms. To catch new recommendations or chats, run your agent on a schedule with list_recommendations and list_conversations.
Can I apply for the Publish API instead?
You can fill in Nextdoor's request form; approval is case by case and aimed at platforms, publishers and agencies. Even approved, it posts and comments but cannot read a business page's posts, recommendations or chats.
Does it work outside the US?
It works in your own account on the Nextdoor site of your country. Nextdoor runs sites for the US, Canada, Australia and Europe, and page features follow what that site offers.
Is the MCP server different from the REST API?
Only in how you call it. Both carry the same 13 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST.
Is Cotlet affiliated with Nextdoor?
No. Cotlet is independent and not affiliated with Nextdoor Holdings.
Can I use the Nextdoor API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.