feat(mcp): add Airtable read-only adapter

[Rudra-G-23]

Summary

Adds a read-only Airtable adapter using scoped Personal Access Token authentication.

Relates to #150.

What changed

• Added airtable_list_bases for base discovery.
• Added airtable_list_tables for table schemas, fields, and views.
• Added airtable_list_records with filterByFormula, view, pageSize, maxRecords, and offset.
• Added airtable_get_record for fetching a single record.
• Registered Airtable in the adapter catalog.
• Uses only data.records:read and schema.bases:read scopes.

All operations are read-only.

Testing

• JSON validation: passed
• catalog.spec.ts: 2388/2388 passed
• git diff --check: passed
• Tested /meta/bases against a real Airtable test base
• Tested /meta/bases/{baseId}/tables
• Tested record listing and pagination
• Tested filterByFormula with {Status}="Completed"
• Tested fetching a single record

The full backend test suite currently hits unrelated Prisma/SCIM TypeScript errors in the local environment. The Airtable catalog validation passes completely.

Notes

The adapter follows the maintainer-requested read-only first cut and uses the existing REST adapter patterns.

cc: @keysersoft

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[github-actions]

👋 Welcome, @Rudra-G-23, and thanks for opening your first PR on AnythingMCP!

A few quick pointers:

• Make sure CI is green before requesting review (Backend, Frontend, Playwright, CodeQL, Trivy).
• If this is a new adapter, the parametrised catalog.spec.ts test will validate it automatically.
• Sign off your commits if you can — it's not blocking, just nice to have.

Someone from the core team will look at this within ~48h. If you don't hear back, please ping us in Discussions / Q&A.

⭐ While you wait — if you find AnythingMCP useful, a star helps others discover it.

[keysersoft]

Reviewed, and it is good. Read only, scoped personal access token, explicit path and query parameters with real example values, and the filterByFormula description shows an actual formula, which is the thing that makes the model use it correctly. I regenerated catalog.ts here and your version matches the generator byte for byte, so you clearly ran the script.

Two notes on the state of the PR.

The backend job was red for a reason that had nothing to do with your work: main moved to 189 adapters while this was open, so the count gate saw "188" in the README. I approved the workflows, merged main into your branch and pushed the bump to 190 across the files that quote the number. Nothing for you to do there.

The CLA is the only thing left. The bot is still red. Post the one line it asks for and I will merge this today.

For a later PR, if you feel like it: fields and sort are the two record parameters people miss most, and /meta/bases itself paginates with an offset once an account has a lot of bases. Neither is worth holding this one up for.

[Rudra-G-23]

I have read the CLA Document and I hereby sign the CLA

[Rudra-G-23]

Done @keysersoft , Thank you for point out

[keysersoft]

CLA is in, thanks. All checks green, and I re-checked the numbers before merging: your branch carries 190 adapter JSONs and quotes 190 everywhere the count gate looks, main is still at 189, so the arithmetic lands right after the merge.

Merging. The website guide, the logo and the marketplace listing are on us, you do not need to do anything else. If you want a second PR on this adapter, fields and sort on the records tool are the two things people ask for.